Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add hiromaily/go-crypto-wallet --skill github-issue-creationgit clone --depth 1 https://github.com/hiromaily/go-crypto-walletWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/hiromaily/go-crypto-wallet/github-issue-creation)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/github-issue-creation"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/github-issue-creation.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00028 | $0.00528 |
| Opus 5 | $0.00014 | $0.00264 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
github-issue-creation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
GitHub Issue Creation
Create issues with proper classification. Labels determine which Skills are used.
Prerequisites
- Load label-context-mapping skill: Use for all label → skill/context mappings
Label Selection Rules
Required Labels
Every issue must have:
- One Type label (
bug,enhancement,refactoring,documentation,security,technical-debt,test) - One Language OR Scope label (
lang:*orscope:*)
Optional Labels
- Chain label: Only for cryptocurrency-specific code
- Test Scope label: Only when Type is
test
Issue Creation Process
1. Classify Task
From user request, determine:
- Type (bug, enhancement, refactoring, documentation, security, technical-debt, test)
- Language OR Scope
- Test scope (if applicable)
- Chain (if applicable)
Use label-context-mapping skill for label → skill/context mappings.
2. Create Proposal
## Proposed Issue
**Title**: [Clear title - 50-72 chars]
**Labels**: [type], [lang/scope], [test scope if applicable], [chain if applicable]
**Skills**: [git-workflow] + [skill based on label-context-mapping]
**Body**:
## Description
[What needs to be done]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
3. Create Issue (After Approval)
gh issue create \
--title "Title" \
--body "Body" \
--label "type,lang/scope,chain"
Quick Reference
Required: [Type] + [Language OR Scope]
Optional: [Test Scope] + [Chain]
→ Labels determine Skills (see label-context-mapping)
→ Skills determine workflow
Related
- label-context-mapping - Label → Skill/Context mapping
- Task Classification SSOT - Label definitions
- fix-issue command - Working on issues
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 86 lines · 28 tokens per session scan A 42c8fb09dee8
github-issue-creation is a skill published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 28 tokens to every session and 528 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.
Other skills, from other repositories
agent-wallet
Operate a non-custodial blockchain wallet on-chain (EVM and Bitcoin), no exchange or MetaMask. Create or import a wallet, balances, send native/ERC-20/BTC, swap tokens, compile/deploy/call Solidity. Trigger on wallet, crypto, ETH, BTC, ERC-20, token, send, transfer, swap, trade, Solidity, contract, on-chain, testnet…
agent-solidity
Write, audit and deploy Solidity smart contracts through a gated multi-step workflow (spec, threat model, design, implementation, in-process EVM proof, security audit, deployment), with a local EVM sandbox that needs no Foundry, Hardhat, anvil, node or funds. Trigger on Solidity, smart contract, .sol, ERC-20, ERC-721…
pqc-scan
Inventory the cryptography in a codebase that a quantum computer would break, and report what the scan could not read. Use when asked about post-quantum readiness, cryptographic inventory, a CBOM, or which algorithms a project signs with.
bytesagain-wallet-tracker
Crypto wallet analytics reference — address formats, on-chain analytics, transaction tracing, hardware wallets, and approval revocation.
github-integration
A coding aid for working with GitHub, a service for hosting code and coordinating software work. It supports creating and querying issues and pull requests and retrieving repository information.
github-manager
Manage GitHub issues and PRs (list, create, comment).