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 sturec5/code-audit-protocolnpx agentmods add plugins/sturec5/code-audit-protocol/marketplacegit clone --depth 1 https://github.com/sturec5/code-audit-protocolGrade A, and why
code-audit-protocol 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": "code-audit-protocol",
"owner": {
"name": "sturec5"
},
"metadata": {
"description": "A 54-phase technology-neutral audit taxonomy, plus domain overlays for the failure classes generic checklists cannot cover",
"version": "1.8.1"
},
"plugins": [
{
"name": "audit-protocol",
"source": "./",
"description": "Audits a code change against a 54-phase failure taxonomy and reports what it did not check, not just what it found. Domain overlays run first and force critical-path treatment.",
"version": "1.8.1",
"author": {
"name": "sturec5"
},
"keywords": [
"audit",
"code-review",
"quality",
"checklist",
"security"
],
"category": "workflow"
}
]
}
What ships with it
1 file beside marketplace.json 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 · 30 lines scan A abbaedd225db
code-audit-protocol is a plugin published in the GitHub repository sturec5/code-audit-protocol (5 stars, last pushed 18d 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-08-31.
Other plugins, from other repositories
logic-lens-marketplace
Plugin marketplace listing 1 plugin: logic-lens.
logic-lens
Logic-first code review using semi-formal execution tracing. Surfaces behavioral bugs, semantic errors, and runtime failures that linters miss.
stometa
Plugin marketplace listing 1 plugin: harness-engineering-skills.
harness-engineering-skills
Two Claude Code engineering skills bundled as one plugin: review-loop (cross-LLM iterative code review with Codex or Gemini as peer) and harness (cybernetics-based Planner→Generator→Evaluator→Retro orchestration for complex tasks).
review-pro
Tiered AI code-review: triage -> relevant specialist reviewers -> synthesis. Built to catch what AI-written code actually ships with — hallucinated APIs, over-engineering, ignored conventions, needless dependencies. Invoke the review-pro skill on a branch or PR.
review-pro
Tiered AI code-review for Claude Code: triage -> relevant specialist reviewers -> synthesis.