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/danielbodnar/skills/format-checkgit clone --depth 1 https://github.com/danielbodnar/skillsWhat 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.00013 | $0.00301 |
| Opus 5 | $0.00006 | $0.00151 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
format-check 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 yesterday.
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
Run a full code quality check on this project using Biome and OxLint. Report all issues found without modifying any files.
Step 1: Run OxLint
Run OxLint to check for lint errors across all TypeScript and JavaScript files:
bunx oxlint
If OxLint reports errors, list each file and the rule violated. Suggest fixes for each issue.
Step 2: Run Biome Check
Run Biome in check mode (no auto-fix) to identify formatting and lint issues:
bunx @biomejs/biome check .
If Biome reports issues, list the files with formatting problems and the specific rules triggered.
Step 3: Summarize Results
After running both tools, provide a summary:
- Total number of files checked
- Number of OxLint errors and warnings
- Number of Biome formatting issues and lint errors
- List of files that need attention, grouped by tool
If there are no issues, confirm the project passes all quality checks.
Auto-Fix Mode
If the user requests fixes, run the tools with auto-fix enabled:
bunx oxlint --fix
bunx @biomejs/biome check --write .
Report what was fixed and whether any issues remain that require manual intervention.
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.
- yesterday First seen · 52 lines · 13 tokens per session scan A 20516c2a65e0
format-check is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 301 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.