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/abdullahmalik17/hacathan_5/sp.implementgit clone --depth 1 https://github.com/AbdullahMalik17/Hacathan_5What 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.00014 | $0.02364 |
| Opus 5 | $0.00007 | $0.01182 |
| Sonnet 5 | $0.00003 | $0.00473 |
| Haiku 4.5 | $0.00001 | $0.00236 |
Grade A, and why
sp.implement 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 2d 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
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 162 lines · 14 tokens per session scan A cfd9be933fc2
sp.implement is a command published in the GitHub repository AbdullahMalik17/Hacathan_5 (9 stars, last pushed 6mo ago), with no licence file. It adds 14 tokens to every session and 2,364 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
install
Install Klag against a Kafka cluster — detects docker/k8s/GitOps, deploys, verifies lag metrics, offers MCP.
diagnose
Triage Kafka consumer lag using a running Klag — rank what is falling behind, diagnose a group, explain the likely cause.
connect
Connect a running Klag's MCP endpoint to this AI client so the agent can query consumer lag directly.
git
Git operations with intelligent commit messages and workflow optimization.
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.