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/oxygen-fragment/claude-modularWrote 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/commands/oxygen-fragment/claude-modular/update-readme)<a href="https://agentmods.dev/commands/oxygen-fragment/claude-modular/update-readme"><img src="https://agentmods.dev/badge/commands/oxygen-fragment/claude-modular/update-readme.svg" alt="Measured on agentmods" 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.00597 |
| Opus 5 | $0.00000 | $0.00298 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
update-readme 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 8d 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.
What it actually says
Update README Command
2. **Content Structure Generation**
- Create comprehensive table of contents
- Generate project description and purpose
- Add installation and setup instructions
- Include usage examples and tutorials
3. **Badge and Status Integration**
- Add CI/CD pipeline status badges
- Include code coverage and quality badges
- Add dependency status indicators
- Include license and version badges
4. **Documentation Links**
- Link to detailed documentation
- Add API documentation references
- Include changelog and release notes
- Link to issue tracker and discussions
5. **Contribution Guidelines**
- Add contribution instructions
- Include code of conduct
- Document development setup
- Add pull request guidelines
6. **Maintenance and Updates**
- Verify all links are working
- Update screenshots and examples
- Refresh dependency information
- Validate installation instructions
# Updated sections:
# - Project description
# - Installation instructions
# - Usage examples
# - Contributing guidelines
```
```bash
# Update README with new feature highlights
/docs:update-readme --highlight-features
# Feature-focused update:
# - New feature descriptions
# - Updated examples
# - Enhanced screenshots
# - Migration guides
```
```bash
# Update README for specific audience
/docs:update-readme --audience=developers
# Developer-focused update:
# - Technical details
# - Architecture overview
# - Development setup
# - API references
```
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.
- 8d ago First seen · 98 lines · 0 tokens per session scan A 342080fd17cb
update-readme is a command published in the GitHub repository oxygen-fragment/claude-modular (283 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 597 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-08-30.
Other commands, from other repositories
paul:help
Show available PAUL commands and usage guide.
paul:verify
Guide manual user acceptance testing of recently built features.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
mutate
Run mutation testing to verify test quality. Builds a custom mutation tool or uses an existing framework, runs mutations, and reports the mutation score with surviving mutants.
analizar-sesiones
Analizar sesiones de Claude en el equipo para extraer patrones de uso y generar recomendaciones de habilidades, plugins, agentes y reglas.
minar-referencias
Buscar repos open-source relevantes como referencia antes de implementar.