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 makefile-updategit 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/makefile-update)<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/makefile-update"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/makefile-update/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hiromaily/go-crypto-wallet/makefile-update"><img src="https://agentmods.dev/badge/skills/hiromaily/go-crypto-wallet/makefile-update.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00424 |
| Opus 5 | $0.00010 | $0.00212 |
| Sonnet 5 | $0.00004 | $0.00085 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
makefile-update 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 9d 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
Makefile Workflow
Workflow for Makefile changes.
Prerequisites
Use git-workflow Skill for branch, commit, and PR workflow.
Applicable Files
| Path | Description |
|---|---|
Makefile |
Main makefile |
make/*.mk |
Included makefiles |
Structure
Makefile # Main entry point, includes make/*.mk
make/
├── go.mk # Go-related targets
├── docker.mk # Docker targets
├── atlas.mk # Database migration targets
├── sqlc.mk # SQLC generation targets
└── ...
Verification Commands
make mk-lint # Lint makefiles
Manual Checks
# List all targets
make help
# Dry run (if supported)
make -n {target}
Guidelines
Style
- Use tabs for indentation (required by Make)
- Use
.PHONYfor non-file targets - Add help text for targets
- Group related targets
Best Practices
- Targets are
.PHONYif not creating files - Dependencies are correct
- Variables use
?=for defaults - Help text exists for main targets
Example Target
.PHONY: my-target
my-target: ## Description of target
@echo "Running my-target..."
command1
command2
Verification Checklist
-
make mk-lintpasses - Target runs correctly
- Dependencies work
- Help text is accurate
Commit Format
chore(make): {brief description}
- {change 1}
- {change 2}
Closes #{issue_number}
Related Skills
git-workflow- Branch, commit, PR workflow
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.
- 9d ago First seen · 96 lines · 21 tokens per session scan A e9ee6fa7ae35
makefile-update is a skill published in the GitHub repository hiromaily/go-crypto-wallet (127 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 424 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.
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…
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.