How do I install the Permission Module skill?

Run npx skillmds@latest add b-open-io/permission-module-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Permission Module safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Permission Module?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Permission Module free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Permission Module?

b-open-io (@b-open-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Permission Module by b-open-io — Agent Skill

Name: Permission Module
Author: b-open-io

Permission Module

This skill should be used when hosting or wiring the 1Sat permission module — WalletPermissionsManager permissionModules, createAssetPermissionModules, view scopes (p 1sat all|collection|app|creator|id), spend labels, apply-on-approve, or @1sat/permission-module-ui prompts. Triggers on 'permission module', 'OneSatPermissionPrompt', 'p 1sat action', 'view scope', 'BRC-165', 'createAssetPermissionModules', or 'grouped permissions'.

b-open-io c8b8f2a 2.5 KB Updated Sep 17, 2026

File contents

1Sat permission module

Gates createAction / listOutputs / internalizeAction for asset schemes. Register on WalletPermissionsManager as permissionModules. Crypto always uses the base wallet, never the gated wrapper.

Host wiring

import { createAssetPermissionModules } from '@1sat/permission-module'
import { OneSatPermissionPrompt } from '@1sat/permission-module-ui'

const modules = createAssetPermissionModules({
  wallet: baseWallet,
  promptHandler: (req) => showPrompt(req),
  adminOriginator,
  permissionStore,
  services,
})

new WalletPermissionsManager(baseWallet, adminOriginator, {
  permissionModules: modules,
})

createAssetPermissionModules builds one module per scheme: 1sat, opns, bsv21, lock. Not BAP / BSocial / sigma.

Mapping

Layer	What	Examples
Storage	plain baskets	`1sat`, `opns`, `bsv21`, `lock`
Spend / dispatch	labels on createAction	`p <scheme> action`, `p <scheme> input id <key>`
View	`listOutputs.basket` grant keys	`p 1sat all\|collection\|app\|creator\|id`

View values live in tags (collection:…, app:…, creator:…, id:…), not the basket name. Module rewrites the basket to the storage name.

collection / app / creator: force tagQueryMode: 'all'
id: auto-allow, leave the caller's query mode
p 1sat opns / p 1sat ordinals are invalid scopes, not baskets

Probe protocol: [0, 'p 1sat probe']. New keys: [0, 'onesat']. Spends use whatever protocolID is in CI.

Apply

After the user approves, onRequest runs embellishCreateActionArgs → applyP1SatCreateAction (ids, Sigma/OpNS seals, script tags including creator: from SIGMA, CI). onResponse finishes sign. Local (no module) uses the same apply in runCreateActionPipeline.

Actions opt in with executeTrackedAction(..., { usePermissionModule: true, permissionScheme: '1sat' }).

UI

@1sat/permission-module-ui renders TransactionPrompt / basket-access prompts. Host supplies promptHandler and resolves true / false.

---name: permission-module-2description: This skill should be used when hosting or wiring the 1Sat permission module — WalletPermissionsManager permissionModules, createAssetPermissionModules, view scopes (p 1sat all|collection|app|creator|id), spend labels, apply-on-approve, or @1sat/permission-module-ui prompts. Triggers on 'permission module', 'OneSatPermissionPrompt', 'p 1sat action', 'view scope', 'BRC-165', 'createAssetPermissionModules', or 'grouped permissions'.---# 1Sat permission moduleGates `createAction` / `listOutputs` / `internalizeAction` for asset schemes. Register on `WalletPermissionsManager` as `permissionModules`. Crypto always uses the **base** wallet, never the gated wrapper.## Host wiring```typescriptimport { createAssetPermissionModules } from '@1sat/permission-module'import { OneSatPermissionPrompt } from '@1sat/permission-module-ui'const modules = createAssetPermissionModules({ wallet: baseWallet, promptHandler: (req) => showPrompt(req), adminOriginator, permissionStore, services,})new WalletPermissionsManager(baseWallet, adminOriginator, { permissionModules: modules,})````createAssetPermissionModules` builds one module per scheme: `1sat`, `opns`, `bsv21`, `lock`. Not BAP / BSocial / sigma.## Mapping| Layer | What | Examples ||-------|------|----------|| Storage | plain baskets | `1sat`, `opns`, `bsv21`, `lock` || Spend / dispatch | labels on createAction | `p <scheme> action`, `p <scheme> input id <key>` || View | `listOutputs.basket` grant keys | `p 1sat all\|collection\|app\|creator\|id` |View values live in **tags** (`collection:…`, `app:…`, `creator:…`, `id:…`), not the basket name. Module rewrites the basket to the storage name.- `collection` / `app` / `creator`: force `tagQueryMode: 'all'`- `id`: auto-allow, leave the caller's query mode- `p 1sat opns` / `p 1sat ordinals` are invalid scopes, not basketsProbe protocol: `[0, 'p 1sat probe']`. New keys: `[0, 'onesat']`. Spends use whatever `protocolID` is in CI.## ApplyAfter the user approves, `onRequest` runs `embellishCreateActionArgs` → `applyP1SatCreateAction` (ids, Sigma/OpNS seals, script tags including `creator:` from SIGMA, CI). `onResponse` finishes sign. Local (no module) uses the same apply in `runCreateActionPipeline`.Actions opt in with `executeTrackedAction(..., { usePermissionModule: true, permissionScheme: '1sat' })`.## UI`@1sat/permission-module-ui` renders `TransactionPrompt` / basket-access prompts. Host supplies `promptHandler` and resolves `true` / `false`.

Frequently asked questions