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/duthaho/skillhub/featurenpx skills add duthaho/skillhub --skill featuregit clone --depth 1 https://github.com/duthaho/skillhubWrote 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/skills/duthaho/skillhub/feature)<a href="https://agentmods.dev/skills/duthaho/skillhub/feature"><img src="https://agentmods.dev/badge/skills/duthaho/skillhub/feature.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.00213 | $0.02159 |
| Opus 5 | $0.00106 | $0.01079 |
| Sonnet 5 | $0.00043 | $0.00432 |
| Haiku 4.5 | $0.00021 | $0.00216 |
Grade A, and why
feature scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
it works (a command, a flow to click through, a curl). When an answer would How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
feature — spec → plan → build, effort-scaled
/feature <description> — start (or resume) a piece of work
/feature — list changes in flight under out/dev/
Answer one question: what is the smallest process that gets THIS change built correctly? The two documented failure modes of workflow suites are opposite: heavyweight gates firing on typo-sized changes, and freestyle sessions shipping unverified scope creep. This skill scales the process to the change — never the other way around.
Step 0 — Size the change (the escape hatch comes first)
Classify before doing anything else, and say which tier you picked:
- Trivial — you could describe the exact diff in one sentence (typo, rename, config value, one-line fix). → No spec, no plan, no folder. Make the change, then run the done gate's evidence checklist inline. Stop here.
- Small — one focused change, ≤ ~3 files, design obvious. → Skip the spec interview; write the plan directly in chat for approval, execute with the Step 3 rules, finish with done. No folder unless the user wants to pause and resume.
- Standard — anything multi-file, multi-session, or with real design decisions. → Full loop below.
If the user explicitly asks for the full treatment ("spec this out"), honor it regardless of size. When genuinely unsure between tiers, pick the smaller one and say so — the plan contract (Step 3) catches scope growth and upgrades the tier if needed.
The change folder — state across sessions
out/dev/<change-slug>/ (<slug> = short change name, lowercased, hyphens;
committing the folder is the user's call — it makes good shared history):
spec.md— what & why, agreed acceptance criteria, decisions/assumptions numbered (D1…/A1…). Written once, then stable.plan.md— the task checklist. Checkboxes are flipped as tasks complete; never delete a task, strike it with a reason instead.log.md— append-only progress journal: one line per task/session (date · task · result · commit). Decisions and surprises go here too.
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.
- 3d ago First seen · 177 lines · 213 tokens per session scan A 400223c60c7f
feature is a skill published in the GitHub repository duthaho/skillhub (9 stars, last pushed 10d ago), licensed MIT. It adds 213 tokens to every session and 2,159 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog.
hook-template
Generate hook script from template. Use when adding a new hook, wiring a PreToolUse/PostToolUse/Stop/Notification hook, or scaffolding hook config for settings.json.
agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
skill-check
Validate skill/command file format and structure. Use after creating or editing a skill, before committing skill changes, or when a skill fails to load or trigger.
agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
session-relay
Continue real repository work between Claude Code, Codex CLI, and Grok Build with a privacy-bounded, drift-aware handoff packet. Use for cross-vendor takeover, context-limit checkpoints, multi-hop Claude→Codex→Grok relays, or receiving an existing Director packet. Use native resume commands for same-CLI history; never…