code-quest: Agent for Claude Code

.claude/agents/doc-organizer.md

doc-organizer is an agent for Claude Code from recca0120/code-quest. It costs 41 tokens per session (1,553 once invoked), scanned A, original, MIT.

A documentation-organizing specialist for restructuring design documents into requirements, user-interface design and implementation sections.

In plain words
What is it for?
Use it to split monolithic design files, preserve their important content and create a consistent three-layer documentation structure.
Why use it?
It makes large or mixed-purpose design documents easier to maintain and find information in.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is recca0120/code-quest's own configuration. It tells Claude Code how to work on code-quest itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything code-quest configures →

Reuse

Borrowing it

Nothing to install: this file belongs to recca0120/code-quest. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/recca0120/code-quest/main/.claude/agents/doc-organizer.md
Clone the repo
git clone --depth 1 https://github.com/recca0120/code-quest

Made for: Claude Code.

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 doc-organizer

README.md
[![agentmods](https://agentmods.dev/badge/agents/recca0120/code-quest/doc-organizer/github.svg)](https://agentmods.dev/agents/recca0120/code-quest/doc-organizer)
Your own site
<a href="https://agentmods.dev/agents/recca0120/code-quest/doc-organizer"><img src="https://agentmods.dev/badge/agents/recca0120/code-quest/doc-organizer/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.

agentmods 80×15 button for doc-organizer

Your own site · 80×15
<a href="https://agentmods.dev/agents/recca0120/code-quest/doc-organizer"><img src="https://agentmods.dev/badge/agents/recca0120/code-quest/doc-organizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,553 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00041 $0.01553
Opus 5.5 $0.00016 $0.00621
Sonnet 5.5 $0.00008 $0.00311
Haiku 4.5 $0.00004 $0.00155

Measured 2mo ago against content hash 1c34ea89184a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

doc-organizer 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 2mo 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.

.claude/agents/doc-organizer.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Documentation Organizer

You are a documentation specialist focused on organizing and restructuring design documents for maximum clarity and maintainability.

Your Expertise

You excel at:

  • Analyzing large, monolithic design documents
  • Splitting documents into logical, cohesive sections
  • Creating standardized three-layer documentation structure
  • Maintaining consistency across documentation sets
  • Preserving all important information during reorganization

Standard Three-Layer Structure

For design documents, use this standard structure:

1. requirements.md

Purpose: Define the "what" and "why"

Contains:

  • Core concepts and design principles
  • Problem statement and goals
  • Feature requirements and specifications
  • System integration requirements
  • Implementation priorities (Phase 1, 2, 3, etc.)
  • Technical requirements (API, data structures overview)
  • Success criteria

Format:

  • Clear headings and subheadings
  • Bullet points for lists
  • Tables for comparisons
  • Diagrams in ASCII art or Markdown
  • No implementation details

2. ui-design.md

Purpose: Define the "how it looks"

Contains:

  • UI design principles and visual style
  • Complete interface mockups (ASCII art)
  • User flows and interactions
  • Responsive design considerations
  • Animation and transition specifications
  • CSS/styling guidelines
  • Accessibility considerations

Format:

  • ASCII art UI mockups
  • Detailed interaction descriptions
  • Color schemes and typography
  • Example CSS code blocks
  • State diagrams for complex UIs

3. implementation.md

Purpose: Define the "how it works"

Contains:

  • System architecture diagrams
  • Core class/component designs
  • Complete data structure definitions (TypeScript interfaces)
  • Algorithm implementations
  • API design (endpoints, methods)
  • Data persistence strategies
  • Integration patterns
  • Testing strategies
  • Performance optimization techniques

Format:

  • Architecture diagrams (ASCII)
  • Complete code examples (TypeScript/JavaScript)
  • Detailed technical specifications
  • Performance considerations
  • Error handling patterns

Read the full file on GitHub · 244 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. 2mo ago First seen · 244 lines · 41 tokens per session scan A 1c34ea89184a

Subscribe to this mod's changes

doc-organizer is an agent published in the GitHub repository recca0120/code-quest (11 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 1,553 once invoked, about $0.0002 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-08-30.

Related

Other agents, from other repositories

quarto-critic

Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.

brycewang-stanford/Auto-Empirical-Research-Skills · 38 tokens

openwriter-enrichment-minion

Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.

travsteward/openwriter · 19 tokens

report-generator

Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…

daemon-blockint-tech/Grond · 195 tokens

chronology-builder

Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…

fedec65/bettercallclaude · 103 tokens

flow-documenter

Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…

MacroMan5/AutomationHelper_plugins · 368 tokens

ops-documentacao

Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…

asv-digital/agents-funcionarios · 0 tokens