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/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/skills)<a href="https://agentmods.dev/commands/regen-coordination/org-os-template/skills"><img src="https://agentmods.dev/badge/commands/regen-coordination/org-os-template/skills.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.00017 | $0.00387 |
| Opus 5 | $0.00009 | $0.00193 |
| Sonnet 5 | $0.00003 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
skills 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 7d 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
You are listing the skills available in this org-os workspace. Follow these steps.
Step 1: Regenerate the skills index
This walks workspace + user + plugin sources, cross-references data/skills-matrix.yaml, and writes SKILLS.md + .well-known/skills.json:
npm run generate:skills
If generate:skills script doesn't exist, fall back to reading data/skills-matrix.yaml and listing skills/ directly.
Step 2: Print the freshly generated SKILLS.md verbatim
The generated file is the single source of truth. Print it as-is — do not reformat, abridge, or re-render. The operator wants to see exactly what the walker found.
cat SKILLS.md
Step 3: Highlight anomalies
If the output includes an "⚠ Anomalies" section (skills with missing SKILL.md, duplicate ids across sources, broken frontmatter), call them out explicitly to the operator as something to fix.
If the output includes "⚠ On disk but not in skills-matrix.yaml", remind the operator that those skills exist on disk but aren't catalogued — they should be added to the matrix or removed from disk.
If the output includes "⚠ In skills-matrix.yaml but missing from disk", flag those as either:
- a stale matrix entry (skill was removed but matrix not updated), or
- an expected promotion candidate that's
in_framework: false
Step 4: Wait for the operator
After printing, ask what they want to do with the listing (e.g., "Want me to promote candidate X?", "Want me to fix anomaly Y?"). Do not act without direction.
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.
- 7d ago First seen · 38 lines · 17 tokens per session scan A 87f696a88ecd
skills is a command published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 387 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.