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 skills add product-on-purpose/agent-skills-toolkit --skill askit-build-commandgit clone --depth 1 https://github.com/product-on-purpose/agent-skills-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/skills/product-on-purpose/agent-skills-toolkit/askit-build-command)<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-build-command"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-build-command/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/product-on-purpose/agent-skills-toolkit/askit-build-command"><img src="https://agentmods.dev/badge/skills/product-on-purpose/agent-skills-toolkit/askit-build-command.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.00692 |
| Opus 5 | $0.00027 | $0.00346 |
| Sonnet 5 | $0.00011 | $0.00138 |
| Haiku 4.5 | $0.00005 | $0.00069 |
Grade A, and why
askit-build-command 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.
How it starts
The opening of the file, as written. The whole thing — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
askit-build-command
Purpose
Author conformant commands. Two modes: create scaffolds a new commands/<name>.md that maps to an existing skill; improve raises an existing command toward the quality bar. On Codex a command is realized as its backing skill (Standard sec 3.2 parity), so this skill emits no Codex artifact. Follows the shared builder pattern. Authoring depth is in references/authoring-commands.md.
When to use
When the user asks to create, scaffold, or improve a slash command for a skill.
create mode
- Brief interview: the command name (kebab-case, becomes
/name), the skill (or workflow) it maps to, optional args, and a description: the LABEL a caller sees beside the slash command, stating what invoking it does. It is not a trigger surface, so do not ask for use-when phrasing (Standard sec 3.2). Skip if provided in context. - Copy
templates/command.mdintocommands/<name>.md. - Fill the frontmatter:
description(the caller-facing label: what invoking it does, non-empty; Standard sec 3.2 - NOT the sec 8.1 skill bar, which does not apply to commands);maps-toequal to the backing skill or workflow name; optionalargument-hint/allowed-tools/model;metadata.version. The filename is the command name (nonamekey). Write a body that invokes the backing skill, passing$ARGUMENTS. - Verify the
maps-totarget exists (a skill inskills/or a workflow in_workflows/). - Register the command in
library.jsoncomponents.commandsas{ name, path, version, tier, status }. - Assess with
node scripts/evaluate.mjs . --jsonand iterate until 0 errors (S3 components index + S7 command-contract must be clean).
improve mode
- Run
node scripts/evaluate.mjs . --jsonand read the report. - For each finding: an S3 error -> declare/undeclare the command in
components.commandsto match disk; an S7 error -> add the missingmaps-to, fix amaps-tothat does not resolve, or add a missingdescription. For any other finding, read its message and apply the fix it states. - Re-run evaluate to confirm.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 33 lines · 54 tokens per session scan A 3c9d0208659e
askit-build-command is a skill published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 692 once invoked, about $0.0003 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 skills, from other repositories
modelchk
Size a task's run before spending it: the cheapest sufficient capability tier (fast, standard, frontier) and the reasoning effort within it, on a neutral scale that binds to whatever levels the model exposes. Use when work seems over- or under-powered, costly, ambiguous, or high-risk, or asks which model class and how…
autobahn
Carve guardrail-adjacent items out of scope with safe alternatives before risk-adjacent work starts, then run the safe remainder at full strength in a fresh subagent that only ever sees the carved prompt, never the risky input. Use when a task includes stealth, scraping, privacy, IP, policy, licensing, security, or…
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
dedash
Remove em-dashes and the dashes standing in for them from a user-owned scope, reading each occurrence in context and choosing the punctuation or wording that fits.