section

section is a command for coding agents from MadeByTokens/claude-code-plugins-madebytokens. It costs 13 tokens per session (703 once invoked), scanned A, original, MIT.

A command for jumping to a named section of a product requirements document, such as users, API design, testing, or risks.

In plain words
What is it for?
Use it to view or edit a specific PRD section by name.
Why use it?
It saves time when working on one part of a long requirements document and shows that section's current status.

Command

Part of the prd plugin — 3 commands shipped together

Install

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.

agentmods
npx agentmods add commands/madebytokens/claude-code-plugins-madebytokens/section
Clone the repo
git clone --depth 1 https://github.com/MadeByTokens/claude-code-plugins-madebytokens

Or install prd, the plugin that ships this one along with the rest of its 3 commands.

Wrote 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.

agentmods badge for section

README.md
[![agentmods](https://agentmods.dev/badge/commands/madebytokens/claude-code-plugins-madebytokens/section.svg)](https://agentmods.dev/commands/madebytokens/claude-code-plugins-madebytokens/section)
Your own site
<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>
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 703 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 4d ago against content hash 34aabaa65588, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/claude-prd-god/commands/section.md · 105 lines

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.

The user wants to jump to a specific section of the PRD.

Arguments

$ARGUMENTS contains the section name. Valid sections:

  • vision or vision_principles
  • problem or problem_statement
  • users or target_users
  • stories or user_stories
  • functional or functional_requirements
  • nonfunctional or non_functional_requirements
  • data or data_model
  • ui or ux or ui_ux_specification
  • api or api_contract
  • change or change_analysis
  • architecture or architecture_decisions
  • edge or edge_cases
  • testing or testing_strategy
  • metrics or success_metrics
  • scope or scope_boundaries
  • risks or risks_mitigations
  • dependencies
  • constraints or technical_constraints
  • evolution or evolution_strategy
  • tech or tech_stack
  • structure or project_structure
  • commands
  • style or code_style
  • git or git_workflow
  • boundaries or ai_boundaries

Actions

  1. Parse the section name from $ARGUMENTS
  2. Read current session file to see section status
  3. Display section content and status
  4. 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"}
      ]
    }
  ]
}

Read the full file on GitHub · 105 lines

Changes

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.

  1. 4d ago First seen · 105 lines · 13 tokens per session scan A 34aabaa65588

Subscribe to this mod's changes

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.