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/madebytokens/claude-code-plugins-madebytokens/sectiongit clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokensWrote 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/madebytokens/claude-code-plugins-madebytokens/section)<a href="https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/section"><img src="https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/section.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 | $0.00013 | $0.00703 |
| Opus 5 | $0.00006 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00141 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
section 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigate to PRD Section
The user wants to jump to a specific section of the PRD.
Arguments
$ARGUMENTS contains the section name. Valid sections:
visionorvision_principlesproblemorproblem_statementusersortarget_usersstoriesoruser_storiesfunctionalorfunctional_requirementsnonfunctionalornon_functional_requirementsdataordata_modeluioruxorui_ux_specificationapiorapi_contractchangeorchange_analysisarchitectureorarchitecture_decisionsedgeoredge_casestestingortesting_strategymetricsorsuccess_metricsscopeorscope_boundariesrisksorrisks_mitigationsdependenciesconstraintsortechnical_constraintsevolutionorevolution_strategytechortech_stackstructureorproject_structurecommandsstyleorcode_stylegitorgit_workflowboundariesorai_boundaries
Actions
- Parse the section name from
$ARGUMENTS - Read current session file to see section status
- Display section content and status
- Offer to work on it
Display Format
SECTION: [Section Name]
Status: [COMPLETE / IN PROGRESS / NOT STARTED]
Current Content:
[Show what's in the session file for this section]
---
Then use AskUserQuestion:
{
"questions": [
{
"question": "What would you like to do with this section?",
"header": "Action",
"multiSelect": false,
"options": [
{"label": "Edit", "description": "Revise or add to this section"},
{"label": "Review", "description": "Check for completeness and issues"},
{"label": "Approve", "description": "Mark this section as complete"},
{"label": "Back", "description": "Return to previous section"}
]
}
]
}
If No Section Specified
If $ARGUMENTS is empty, show section list and ask which one:
{
"questions": [
{
"question": "Which section would you like to work on?",
"header": "Section",
"multiSelect": false,
"options": [
{"label": "Problem Statement", "description": "Section 1 - Why this exists"},
{"label": "Target Users", "description": "Section 2 - Who it's for"},
{"label": "User Stories", "description": "Section 3 - What users can do"},
{"label": "Other section...", "description": "Type the section name"}
]
}
]
}
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.
- 4d ago First seen · 105 lines · 13 tokens per session scan A 34aabaa65588
section is a command published in the GitHub repository MadeByTokens/claude-code-plugins-madebytokens (2 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 703 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.