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 agents/recca0120/code-quest/doc-organizergit clone --depth 1 https://github.com/recca0120/code-questWhat 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.00041 | $0.01553 |
| Opus 5 | $0.00020 | $0.00776 |
| Sonnet 5 | $0.00008 | $0.00311 |
| Haiku 4.5 | $0.00004 | $0.00155 |
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 2d 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 — 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
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.
- 2d ago First seen · 244 lines · 41 tokens per session scan A 1c34ea89184a
doc-organizer is an agent published in the GitHub repository recca0120/code-quest (11 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 1,553 once invoked, about $0.0002 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.