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.
git 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/manage-scheduling-links)<a href="https://agentmods.dev/commands/chili-piper/mcp-assets/manage-scheduling-links"><img src="https://agentmods.dev/badge/commands/chili-piper/mcp-assets/manage-scheduling-links/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/commands/chili-piper/mcp-assets/manage-scheduling-links"><img src="https://agentmods.dev/badge/commands/chili-piper/mcp-assets/manage-scheduling-links.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.00038 | $0.00392 |
| Opus 5.5 | $0.00015 | $0.00157 |
| Sonnet 5.5 | $0.00008 | $0.00078 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
manage-scheduling-links 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 1mo 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.
- 1mo ago First seen · 26 lines · 38 tokens per session scan A 4aef30f9bcf7
manage-scheduling-links is a command published in the GitHub repository Chili-Piper/mcp-assets (8 stars, last pushed 2d ago), with no licence file. It adds 38 tokens to every session and 392 once invoked, about $0.0002 per session on Opus 5.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
cs-internal-comms
Internal-only change-management comms using ADKAR (Prosci) + Kotter's 8-step. NOT marketing (external) and NOT executive narrative strategy. Direct invocation of the internal-comms skill.
cs-process-map
Map an internal business process (BPMN-style swim lanes), measure cycle time, and detect bottlenecks where work spends most of its time waiting. Direct invocation of the process-mapper skill.
runs
List live and persisted CCAM-launched Claude Code and Codex runs.
project-health
Audit and manage project configuration — permissions, context, docs.
tasks
../../vertical-plugins/scenarios/commands/tasks.md.
stat
A project-status command for an embedded-software project. It reads saved project notes and shows the current state, progress, next action, or a fuller project overview.