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 skills/cubxxw/agent-kit/manage-agent-kitnpx skills add cubxxw/agent-kit --skill manage-agent-kitgit clone --depth 1 https://github.com/cubxxw/agent-kitWrote 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/cubxxw/agent-kit/manage-agent-kit)<a href="https://agentmods.dev/skills/cubxxw/agent-kit/manage-agent-kit"><img src="https://agentmods.dev/badge/skills/cubxxw/agent-kit/manage-agent-kit.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.00093 | $0.00957 |
| Opus 5 | $0.00046 | $0.00478 |
| Sonnet 5 | $0.00019 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00096 |
Grade A, and why
manage-agent-kit 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 6d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage Agent Kit
Treat the checked-out agent-kit repository as the canonical source. Agent
hosts receive views of the same skill directories through symlinks.
Start with evidence
- Run
./bin/agent-kit doctor --strict. - Run
./bin/agent-kit status --profile full-stack --tool core. - Inspect
catalog.jsonbefore proposing changes. - Read references/operations.md for the relevant operation.
Do not silently replace a real directory or a symlink owned by another tool. Report the exact conflict and preserve it.
Install or repair links
Use the smallest applicable profile:
base: only this management skill.developer: source-grounded engineering and agent infrastructure.design: recursive direction branching, UI/UX evidence, and frontend preflight.full-stack: recommended personal workstation.top: every broadly useful skill that passed the full adoption gate.all: compatibility alias fortop.
Preview first:
./bin/agent-kit install --profile full-stack --tool core --dry-run
Then install. Use --replace-managed only for stale symlinks that already
point into this checkout. It must never replace copied files or foreign links.
Curate a new skill
Read the checkout’s
docs/top-skills.md
before broad discovery. It separates adopted, on-demand, and discovery-only
sources.
Accept a skill only when all gates pass:
- It solves a repeated, current task with clear marginal value.
- It does not duplicate a host-provided or already installed capability.
- Its source is attributable, actively maintained, and pinned to a full commit SHA.
- Its redistribution license is explicit. Do not vendor an unlicensed skill.
- Read every executable file and inspect network, credential, and destructive behavior.
- Add it to
catalog.jsonand the narrowest profile. - Run the creator validator when first-party skill instructions change.
- Run the repository tests,
doctor --strict, and the public safety scan. - Install it into the intended hosts and verify every link resolves to the same target.
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.
- 6d ago First seen · 113 lines · 93 tokens per session scan A 802c66eec5d8
manage-agent-kit is a skill published in the GitHub repository cubxxw/agent-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 93 tokens to every session and 957 once invoked, about $0.0005 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
fieldops-ctf-reverse
Reverse engineering of compiled, packed, virtualized, or obfuscated targets for authorized CTF challenges. Use when the task is to understand, decompile, disassemble, or unpack an unknown executable across ELF, PE, Mach-O, APK, WASM, firmware, bytecode, or custom-VM targets.
fieldops-ctf-writeup
Generate a submission-style writeup for a solved CTF challenge. Use after a solve, when the user wants a reproducible competition report covering metadata, ordered solution steps, the solve script, and the recovered flag.
fieldops-powershell-utf8
Writes, reviews, and repairs PowerShell so Persian/Farsi and other Unicode text survives console input, console output, native-process pipelines, and file I/O. Use when text turns into mojibake or question-mark boxes, when a UTF-8 BOM must be added or removed, for multilingual or non-ASCII automation, or when a script…
fieldops-ctf-operator
Triage, route, and validate authorized CTF investigations. Use when the category is unknown, the user is stuck, evidence conflicts, or a claimed solve must be reproduced from a clean baseline. Dispatches to the most relevant fieldops-ctf- specialist.
fieldops-prompt-decorators
Interprets and executes Prompt Decorators written with +++Name(key=value) syntax, handling message vs. chat scope, parameter validation, decorator composition, conflict resolution, meta-decorator expansion (N2 and Storm), retained-state inspection (ActiveDecs and AvailableDecs), selective clearing, and conversation…
fieldops-research
Investigates externally verifiable, uncertain, current, comparative, or high-consequence questions and delivers concise, evidence-backed, actionable answers. Use when facts may have changed, claims need fact-checking, sources disagree, the user wants a recommendation or comparison (which is better, is it still true…