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 skills add supportersimulator/3-surgeons --skill doc-organizergit clone --depth 1 https://github.com/supportersimulator/3-surgeonsWrote 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/skills/supportersimulator/3-surgeons/doc-organizer)<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/doc-organizer"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/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.
<a href="https://agentmods.dev/skills/supportersimulator/3-surgeons/doc-organizer"><img src="https://agentmods.dev/badge/skills/supportersimulator/3-surgeons/doc-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.00025 | $0.01432 |
| Opus 5 | $0.00013 | $0.00716 |
| Sonnet 5 | $0.00005 | $0.00286 |
| Haiku 4.5 | $0.00003 | $0.00143 |
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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Organizer -- 4-Folder Document System
What This Does
Sets up a 4-folder document system that separates ideas from specs from code reality from proven patterns. Each folder has a different trust level. Documents don't move between folders -- each generates independently.
The Four Folders
| Folder | What Goes Here | Trust | Who Writes It |
|---|---|---|---|
docs/inbox/ |
Raw ideas, chat exports, research notes | LOW | Anyone. Append-only. Never deleted. |
docs/vision/ |
Specs, designs, architecture decisions | MEDIUM | Human + AI collaboration (brainstorming, cross-exam) |
docs/reflect/ |
What the code actually does today | HIGH | Written FROM code analysis, not from specs |
docs/dao/ |
Patterns validated through evidence | HIGHEST | Emerges from outcomes, changes only with proof |
When to Invoke This Skill
- Project setup -- user runs
3s docs-initor asks about document organization - Onboarding -- new team member or AI agent needs to understand the knowledge structure
- Drift detected -- documents are accumulating without structure, or specs diverge from reality
Setup Process
Step 1: Detect Project Structure
Before creating folders, evaluate the project:
- Single repo? -- Create one set of 4 folders at
docs/ - Monorepo with distinct projects? -- Each project that has its own domain, its own codebase concerns, and its own decision history deserves its own 4 folders
- Superrepo with submodules? -- Each submodule gets its own 4 folders. The superrepo gets cross-cutting 4 folders for ecosystem-level docs.
How to decide if a subdirectory deserves its own 4 folders:
- Does it have its own README or documentation?
- Does it make architectural decisions independently?
- Could someone work on it without understanding the rest of the repo?
- Does it have (or should it have) its own tests?
If yes to 2+ of these, it deserves its own 4 folders.
Step 2: Create Folders
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.
- 10d ago First seen · 143 lines · 25 tokens per session scan A 952a0117ae0d
doc-organizer is a skill published in the GitHub repository supportersimulator/3-surgeons (2 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,432 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 skills, from other repositories
skill-creator
Create, install, or update skills in the workspace. Use when (1) installing a skill from a URL or remote source, (2) creating a new skill from scratch, (3) updating or restructuring existing skills. Always use this skill for any skill installation or creation task.
image-generation
Generate or edit images from text prompts. Use when the user asks to create, draw, design, or edit an image, illustration, photo, icon, poster, or any visual content.
deepcode-self-refer
Answers questions about Deep Code CLI itself — including features, configuration options, slash commands, Skills, MCP integration, permissions, notifications, session persistence, and troubleshooting. Use this when users ask how to configure or use Deep Code, how to set up an MCP server, configure notifications (such…
image-generator
Generate or edit images from text and local files, image URLs, or data URLs through image API. Use when the user asks to create an image, generate from one or more reference images, combine styles or elements across references, or edit a marked region while blending the result into the original scene.
weibo-poster
A writing guide for Weibo, a Chinese microblogging platform similar to a short-post social network. It covers concise posts, longer posts, hashtags, @ mentions, image layouts, and posting-time suggestions.
excel-helper
A spreadsheet assistant for Excel, a program used to organize, calculate, and analyze tabular data. It covers formulas, pivot tables, charts, data cleaning, and VBA macros, which are small automation programs for Excel.