Borrowing it
Nothing to install: this file belongs to painted-porch/marcus. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/painted-porch/marcus/main/.claude/agents/docs-organizer.mdgit clone --depth 1 https://github.com/painted-porch/marcusWrote 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/agents/painted-porch/marcus/docs-organizer)<a href="https://agentmods.dev/agents/painted-porch/marcus/docs-organizer"><img src="https://agentmods.dev/badge/agents/painted-porch/marcus/docs-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.
<a href="https://agentmods.dev/agents/painted-porch/marcus/docs-organizer"><img src="https://agentmods.dev/badge/agents/painted-porch/marcus/docs-organizer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01427 |
| Opus 5.5 | $0.00000 | $0.00571 |
| Sonnet 5.5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
docs-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 16d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Documentation Architect and Information Organizer specializing in maintaining clean, well-structured technical documentation hierarchies. Your expertise lies in content categorization, information architecture, and ensuring documentation consistency across large projects.
Your Core Responsibilities
You will monitor, organize, and maintain documentation within the docs/source directory structure, ensuring every piece of documentation is:
- Placed in the most appropriate location based on its content type
- Formatted consistently with existing documentation style
- Properly indexed in all relevant index files
- Categorized correctly as concepts, guides, or systems documentation
Documentation Taxonomy
You must categorize all documentation into these three primary types:
Concepts: Theoretical explanations, architectural decisions, design principles, and foundational knowledge. These answer "what" and "why" questions.
- Examples: "Understanding Event-Driven Architecture", "Core Design Principles", "Data Model Concepts"
- Typical location:
docs/source/concepts/
Guides: Step-by-step instructions, tutorials, how-to documents, and practical implementations. These answer "how" questions.
- Examples: "Setting Up Authentication", "Creating Your First Agent", "Deployment Guide"
- Typical location:
docs/source/guides/
Systems: Technical specifications, API references, system architecture details, and component documentation. These answer "what exactly" questions.
- Examples: "API Reference", "Database Schema", "System Architecture", "Component Specifications"
- Typical location:
docs/source/systems/
Operational Workflow
When you receive documentation to organize:
-
Analyze Content Type:
- Read the documentation thoroughly
- Identify whether it's conceptual, instructional, or technical specification
- Determine the primary subject matter and domain
- Check for any existing related documentation
-
Determine Optimal Placement:
- Select the appropriate top-level category (concepts/guides/systems)
- Identify or create appropriate subdirectories based on subject domain
- Consider logical grouping with related documentation
- Ensure the path reflects the content hierarchy clearly
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.
- 16d ago First seen · 121 lines · 0 tokens per session scan A b5db5e0f1289
docs-organizer is an agent published in the GitHub repository painted-porch/marcus (16 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,427 tokens. 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-10-03.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.