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 commands/softaworks/agent-toolkit/sync-skills-readmegit clone --depth 1 https://github.com/softaworks/agent-toolkitWrote 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/softaworks/agent-toolkit/sync-skills-readme)<a href="https://agentmods.dev/commands/softaworks/agent-toolkit/sync-skills-readme"><img src="https://agentmods.dev/badge/commands/softaworks/agent-toolkit/sync-skills-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 | $0.00012 | $0.01259 |
| Opus 5 | $0.00006 | $0.00629 |
| Sonnet 5 | $0.00002 | $0.00252 |
| Haiku 4.5 | $0.00001 | $0.00126 |
Grade A, and why
sync-skills-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 4d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync Skills README
Update the root README.md "Available Skills" table with all skills currently in the skills/ directory. This command scans skills, reads their metadata, categorizes them, and regenerates the table.
Workflow
1. Scan Skills Directory
Use Bash to list all skill directories:
ls -1 skills/
For each skill directory found, proceed to step 2.
2. Extract Skill Metadata
For each skill, read the SKILL.md frontmatter to extract:
name:field (skill identifier)description:field (what the skill does)
Use the Read tool to read skills/[skill-name]/SKILL.md and extract the YAML frontmatter between the --- markers.
Example:
---
name: codex
description: Use when the user asks to run Codex CLI for code analysis...
---
Extract both fields for table generation.
3. Categorize Skills
Assign each skill to a category based on its purpose. Use this mapping:
| Category | Emoji | Keywords in name/description |
|---|---|---|
| AI Tools | 🤖 | codex, gemini, perplexity, ai, llm, model |
| Meta | 🔮 | command-creator, plugin-forge, plugin, command |
| Documentation | 📝 | docs, documentation, handoff, requirements, diagram, mermaid, draw, excalidraw, marp, slide, c4-architecture |
| Development | 🛠️ | session, handoff, entropy, development, workflow, database, dependency |
| Design & Frontend | 🎨 | design, frontend, ui, openapi, typescript, system |
| Utilities | 🔧 | domain, meme, web-to-markdown, utility, tool, datadog |
| Planning | 🎯 | plan, planning, spec, forge, gepetto, requirements, clarity, game-changing, features |
| Professional | 👔 | professional, communication, career, soft-skill, feedback, conversation |
| Testing | 🧪 | test, testing, qa, quality |
| Git | 📦 | commit, git, branch, pr, pull-request |
Categorization logic:
- Check the skill name and description (case-insensitive)
- Match against keywords in the table above
- Assign to the first matching category
- If no match, default to "Utilities" (🔧)
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.
- 4d ago First seen · 148 lines · 12 tokens per session scan A 154b427700f4
sync-skills-readme is a command published in the GitHub repository softaworks/agent-toolkit (2,422 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 1,259 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 commands, from other repositories
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
speckit.opsmill.retrospect
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
create-issue
Transform feature descriptions, bug reports, or improvement ideas into well-structured GitHub issues.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.