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.
/plugin marketplace add Kasempiternal/Claude-Agent-Systemnpx agentmods add plugins/kasempiternal/claude-agent-system/casgit clone --depth 1 https://github.com/Kasempiternal/Claude-Agent-SystemWrote 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/plugins/kasempiternal/claude-agent-system/cas)<a href="https://agentmods.dev/plugins/kasempiternal/claude-agent-system/cas"><img src="https://agentmods.dev/badge/plugins/kasempiternal/claude-agent-system/cas.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cas 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
{
"name": "cas",
"version": "7.37.0",
"description": "Evidence-driven research, guarded Codex delegation, explicit native parallelism, secret protection, and approval gates for rm, commit, and push.",
"source": "./claude-agent-system-plugin"
}What ships with it
1 file beside marketplace.json#cas 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.
- yesterday First seen · 6 lines scan A ba23679c3f13
cas is a plugin published in the GitHub repository Kasempiternal/Claude-Agent-System (15 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
manifest-dev-tools
Tools for prompts and PRs alongside the manifest workflow. Includes collaborative PR walkthroughs, autonomous PR review with independent per-gate manifest verification, author-side PR babysitting that forwards /do verification policy, gap-calibrated prompt engineering, cross-boundary context handoff, incremental…
privacy-guard
Keeps private infrastructure details out of public repositories. Ships the privacy-guard skill: session rules for what must never cross the public boundary, plus a per-repo pre-commit gate built on a gitignored local denylist and gitleaks. The denylist is never committed, so the hook is a no-op for external…
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
odin
ODIN - advanced code agent with diagram-first engineering and atomic commit workflows for surgical precision in software development.
gates
Four stateless PreToolUse gates, a PostToolUse JSON-config guard, and a docs-consolidation trigger. Denies a git commit that changes code without staging its covering docs (per-plugin README/CLAUDE.md pairs, or the nearest README/CLAUDE/AGENTS walking up); asks before a new-project scaffold command (npm create vite…
coding
Opinionated Claude Code workflow skills: clear and unambiguous technical writing (write-clearly), iterative planning (replan), proof-based code review (review, review-staged, second-opinion), disciplined Conventional-Commit staging (gitplan, stage), and the Technical Project Plan workflow (tpp, handoff…