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 agentmods add commands/kodroi/block/creategit clone --depth 1 https://github.com/kodroi/blockWhat 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 | $0.00021 | $0.01246 |
| Opus 5 | $0.00010 | $0.00623 |
| Sonnet 5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
create 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.block Creator
This command helps you create .block and .block.local files to protect directories from Claude Code modifications.
When to Use
- User wants to protect a directory from Claude modifications
- User asks about .block files
- User wants to restrict which files Claude can edit
- User says "lock", "protect", or "restrict" in context of files/directories
- User wants local/personal protection rules that aren't committed to git
.block Format Reference
Block All (Empty or {})
{}
Blocks all file modifications in the directory.
Allowed List Mode
{
"allowed": ["*.test.ts", "tests/**/*"]
}
Only files matching these patterns can be edited.
Blocked List Mode
{
"blocked": ["*.config.js", "secrets/**/*"]
}
Files matching these patterns are protected; all others can be edited.
With Guide Messages
{
"blocked": ["migrations/**/*"],
"guide": "This directory contains database migrations. Ask the user before modifying."
}
Pattern-Specific Guides
{
"blocked": [
{ "pattern": "*.env*", "guide": "Environment files contain secrets." }
]
}
Workflow
Step 1: Ask File Type
Use AskUserQuestion to determine whether to create a main or local file:
Question: "Should this be a shared or local configuration?"
Header: "File type"
Options:
1. "Shared (.block)" - "Committed to git, shared with team"
2. "Local (.block.local)" - "Not committed, personal/machine-specific rules"
Step 2: Ask Protection Mode
Use AskUserQuestion to determine the protection mode:
Question: "What type of protection do you need?"
Header: "Mode"
Options:
1. "Block all" - "Prevent all modifications in this directory"
2. "Allowed list" - "Only allow specific file patterns to be edited"
3. "Blocked list" - "Protect specific file patterns, allow everything else"
Step 3: Ask Directory Location
Question: "Where should the configuration file be created?"
Header: "Location"
Options:
1. "Current directory" - "Create in the current working directory"
2. "Specify path" - "Enter a custom directory path"
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.
- yesterday First seen · 184 lines · 21 tokens per session scan A f877bad40a97
create is a command published in the GitHub repository kodroi/block (2 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 1,246 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-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.