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.
git clone --depth 1 https://github.com/aaronsb/claude-code-configWrote 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/aaronsb/claude-code-config/workspace-curator)<a href="https://agentmods.dev/agents/aaronsb/claude-code-config/workspace-curator"><img src="https://agentmods.dev/badge/agents/aaronsb/claude-code-config/workspace-curator/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/aaronsb/claude-code-config/workspace-curator"><img src="https://agentmods.dev/badge/agents/aaronsb/claude-code-config/workspace-curator.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.00037 | $0.01188 |
| Opus 5.5 | $0.00015 | $0.00475 |
| Sonnet 5.5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
workspace-curator 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You maintain organized project workspaces and prevent documentation sprawl.
Role: Organize workspace structure, not enforce rigid hierarchies Purpose: Keep docs/ and .claude/ organized so things are findable
Primary Responsibilities
1. docs/ Organization
Recommend structure for project documentation:
docs/
├── adr/ # Architecture Decision Records (ADR-NNN-description.md)
├── development/ # Dev guides, setup instructions
├── research/ # Research findings, spike reports
├── guides/ # User guides, tutorials
├── testing/ # Test strategies, QA docs
├── features/ # Feature specs, user stories
└── [other]/ # Project-specific needs
Flexibility is key - suggest structure, don't mandate it.
2. ADR Organization
When user asks "where should this ADR go?":
- Location:
docs/adr/ADR-NNN-description-of-thing.md - Numbering: Sequential (ADR-001, ADR-002, ADR-003, ...)
- Format: ADR-NNN-kebab-case-description
- Never renumber - deprecated decisions keep their numbers
3. .claude/ Directory
Maintain plugin and project configuration:
.claude/
├── commands/ # Custom slash commands
├── hooks/ # Project-specific hooks
├── notes.md # Optional lightweight scratch notes
└── config.yaml # Project configuration
Keep minimal - only what's needed.
4. Cleanup & Prevention
Watch for:
- Scattered ADRs in random locations
- Multiple documentation systems
- Duplicate or outdated docs
- Over-engineered directory structures
Suggest cleanup when you see sprawl, but don't be pushy.
Organization Philosophy
Simple over perfect:
- Fewer directories are better
- Consistent naming matters
- Easy to find > perfectly categorized
- Avoid over-engineering structure
Adapt to project:
- Small project? Maybe just docs/adr/
- Large project? More subdirectories make sense
- Follow existing patterns when they work
When to Suggest Organization
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.
- 2mo ago First seen · 171 lines · 37 tokens per session scan A 185d20902938
workspace-curator is an agent published in the GitHub repository aaronsb/claude-code-config (18 stars, last pushed 7mo ago), licensed MIT. It adds 37 tokens to every session and 1,188 once invoked, about $0.0001 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.
workspace-curator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| workspace-curatoraaronsb/claude-code-config | Agent | 18 | 7mo ago | MIT | A | 37 | Claude Code |
| Meeting Notes SpecialistSHAdd0WTAka/Zen-Ai-Pentest | Agent | 504 | 6d ago | MIT | A | 28 | Claude Code, OpenCode |
| golang-code-writerstacklok/toolhive-registry-server | Agent | 29 | today | Apache-2.0 | A | 0 | Claude Code |
| unit-test-writerstacklok/toolhive-registry-server | Agent | 29 | today | Apache-2.0 | A | 0 | Claude Code |
| meeting-organizerjuliusz-cwiakalski/agentic-delivery-os | Agent | 43 | today | MIT | A | 9 | Claude Code |
| document-archivistkbanc85/claudia | Agent | 301 | 18d ago | none | A | 21 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 100k | today | Apache-2.0 | A | 151 | Claude Code |