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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/commands/matt-dionis/claude-code-configs/create-tool)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/create-tool"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/create-tool/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/commands/matt-dionis/claude-code-configs/create-tool"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/create-tool.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.00010 | $0.00466 |
| Opus 5.5 | $0.00004 | $0.00186 |
| Sonnet 5.5 | $0.00002 | $0.00093 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
create-tool 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 1mo 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
Create Token-Gated Tool
Create a new FastMCP tool with token protection using the Radius MCP SDK.
Parameters: $ARGUMENTS
Tool Creation Steps
-
Parse Arguments
- Extract tool name, token ID, and optional tier
- Validate token ID format
- Determine appropriate access pattern
-
Generate Tool Implementation
server.addTool({
name: '{tool_name}',
description: '{description} (requires token {token_id})',
parameters: z.object({
// Define your parameters here
input: z.string().describe('Input data'),
options: z.object({
format: z.enum(['json', 'text']).optional(),
verbose: z.boolean().optional()
}).optional(),
__evmauth: z.any().optional().describe('Authentication proof')
}),
handler: radius.protect({token_id}, async (args) => {
// Tool implementation
try {
// Process the input
const result = await process{ToolName}(args.input, args.options);
// Return MCP-formatted response
return {
content: [{
type: 'text',
text: JSON.stringify(result, null, 2)
}]
};
} catch (error) {
throw new Error(`{tool_name} failed: ${error.message}`);
}
})
});
-
Add to Appropriate Tier
- Map to correct token tier
- Update TOOL_REQUIREMENTS mapping
- Document access requirements
-
Create Test Case
- Unit test for the tool
- Auth flow test
- Error handling test
-
Update Documentation
- Add to tool registry
- Document parameters
- Include usage examples
Generate Complete Tool
Based on the arguments provided, create:
- Tool implementation file
- Test file
- Documentation update
- Integration with existing server
The tool should follow FastMCP best practices and properly integrate with the Radius MCP SDK for token protection.
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.
- 1mo ago First seen · 80 lines · 10 tokens per session scan A aa5309253c62
create-tool is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 10 tokens to every session and 466 once invoked, about $0.0000 per session on Opus 5.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-03.
Other commands, from other repositories
deploy
Deploy a program to devnet, or to mainnet after the user's explicit go-ahead.
connect-vybe
Connect and authenticate the Vybe Solana MCP server over OAuth.
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
audit-strict
Multi-pass consensus audit — runs the audit twice with different prompts, only reports consensus findings. Aggressively cuts false positives.
docs-remove
Remove a user-defined source alias from sources.yaml, optionally deleting its cached Markdown.
checklist
Generate a custom checklist for the current feature based on user requirements.