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 skills/saolalab/clawforce/documentationnpx skills add saolalab/clawforce --skill documentationgit clone --depth 1 https://github.com/saolalab/clawforceWhat 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.00016 | $0.00435 |
| Opus 5 | $0.00008 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
documentation 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.
What it actually says
Documentation
Content Types (Diátaxis)
| Type | Purpose | User Need |
|---|---|---|
| Tutorial | Learning | "Show me how" |
| How-to | Tasks | "Help me do X" |
| Reference | Information | "What are the details?" |
| Explanation | Understanding | "Help me understand" |
Tutorial Template
# [Title]: Getting Started with [Feature]
## What You'll Learn
- Skill 1
- Skill 2
## Prerequisites
- Requirement 1
- Requirement 2
## Steps
### Step 1: [Action]
[Explanation]
```code
example
Step 2: [Action]
[Explanation]
Next Steps
- [Link to related tutorial]
- [Link to reference]
## How-to Template
```markdown
# How to [Task]
## Overview
Brief description of what this guide covers.
## Prerequisites
- Requirement 1
## Steps
1. **Do this first**
[Explanation if needed]
2. **Then do this**
```code
example
Troubleshooting
Common Issue
Solution to common issue.
Related
- [Link to related content]
## Writing Guidelines
### Clarity
- Use active voice
- Keep sentences short
- One idea per paragraph
- Use consistent terminology
### Structure
- Lead with the most important info
- Use headings for scanability
- Include code examples
- Add visual aids
### Accessibility
- Use descriptive link text
- Add alt text to images
- Ensure proper heading hierarchy
- Consider screen readers
## Documentation Review Checklist
- [ ] Technically accurate
- [ ] Clear and concise
- [ ] Follows style guide
- [ ] Code examples tested
- [ ] Links working
- [ ] Images have alt text
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 · 108 lines · 16 tokens per session scan A 2fcf41836757
documentation is a skill published in the GitHub repository saolalab/clawforce (38 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 435 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-30.
Other skills, from other repositories
swmm-modeling-memory
Read historical Agentic SWMM experiment audit artifacts and summarize repeated assumptions, QA issues, failures, missing evidence, run-to-run differences, lessons learned, and controlled skill update proposals. Use downstream of swmm-experiment-audit when multiple audited runs exist or when a user asks for modeling…
self-improvement
Captures learnings, errors, and corrections to enable continuous improvement. Use when: (1) A command or operation fails unexpectedly, (2) User corrects Claude ('No, that's wrong...', 'Actually...'), (3) User requests a capability that doesn't exist, (4) An external API or tool fails, (5) Claude realizes its knowledge…
codebase-to-course
Turn a local folder or GitHub repository into an interactive browser-based course that explains how the codebase works for non-expert programmers and AI-assisted builders. Use when a user asks to make a course, tutorial, walkthrough, learning guide, codebase explanation, or interactive lesson from a project.
testing-course-samples
Use when asked to validate, test, smoke-test, or run the course's notebook and code samples against a live Microsoft Foundry / Azure OpenAI configuration. Covers environment setup (.env, az login, packages), the scripts/validate-notebooks.ps1 runner, interpreting PASS/FAIL results, and which lessons need extra…
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…