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/chili-piper/mcp-assets/check-availabilitygit clone --depth 1 https://github.com/Chili-Piper/mcp-assetsWrote 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/chili-piper/mcp-assets/check-availability)<a href="https://agentmods.dev/commands/chili-piper/mcp-assets/check-availability"><img src="https://agentmods.dev/badge/commands/chili-piper/mcp-assets/check-availability.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.00031 | $0.00271 |
| Opus 5 | $0.00015 | $0.00135 |
| Sonnet 5 | $0.00006 | $0.00054 |
| Haiku 4.5 | $0.00003 | $0.00027 |
Grade A, and why
check-availability 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 5d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 21 lines · 31 tokens per session scan A 45412b144483
check-availability is a command published in the GitHub repository Chili-Piper/mcp-assets (7 stars, last pushed yesterday), with no licence file. It adds 31 tokens to every session and 271 once invoked, about $0.0002 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
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
adopt-ai-properly
Workflow recipe — the org-side AI adoption arc, policy to proof, by chaining 4 skills.
land-a-job
Workflow recipe — go after a specific role end to end by chaining 4 skills: decode the JD, research the company, tailor your application, and prep the interview.
launch-an-ai-feature
Workflow recipe — take an AI/LLM feature from a probabilistic-aware PRD to a launch-ready model card by chaining 5 skills.
repurpose
Workflow recipe — turn one blog post, video, or idea into a full platform-native content pack (thread, LinkedIn, newsletter, carousel, short-form script) with sharp hooks and a thumbnail concept.