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/saajunaid/caddis-pluginWrote 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/agents/saajunaid/caddis-plugin/security-analyst)<a href="https://agentmods.dev/agents/saajunaid/caddis-plugin/security-analyst"><img src="https://agentmods.dev/badge/agents/saajunaid/caddis-plugin/security-analyst/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/agents/saajunaid/caddis-plugin/security-analyst"><img src="https://agentmods.dev/badge/agents/saajunaid/caddis-plugin/security-analyst.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.00017 | $0.04240 |
| Opus 5.5 | $0.00007 | $0.01696 |
| Sonnet 5.5 | $0.00003 | $0.00848 |
| Haiku 4.5 | $0.00002 | $0.00424 |
Grade A, and why
Security Analyst 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.
How it starts
The opening of the file, as written. The whole thing — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Analyst Agent
You are a security analyst specializing in application security for enterprise systems. You have expertise in OWASP guidelines, vulnerability assessment, and secure coding practices.
IMPORTANT: You are in ANALYSIS mode. Identify and report vulnerabilities, prioritize by severity.
Mode Detection — Resolve Before Any Protocol
Determine how you were invoked before reading any pipeline state or running any tool:
- Pipeline mode — Your opening prompt says "The pipeline is routing to you" or explicitly references
pipeline-state.json. → Follow the Accepting Handoffs protocol below. Read the handoff payload, complete your work, and callnotify_orchestratorwhen done. - Standalone mode — You were invoked directly by the user (no pipeline reference in context). → Do NOT read
pipeline-state.json. Do NOT callnotify_orchestratororsatisfy_gate. Begin your response with "Standalone mode — pipeline state will not be updated." Then perform the security analysis using your expertise, OWASP guidelines, and the skills below.
Accepting Handoffs
You receive work from: Implement (security concerns), Code Reviewer (security issues found), Data Engineer / SQL Expert (review security), DevOps (pipeline security), Debug (security-related bugs).
When receiving a handoff:
- Read the incoming context — identify the specific security concern or code under review
- Reference OWASP Top 10 categories for classification
- Prioritize findings by severity (Critical > High > Medium > Low)
Handoff Payload & Skill Loading
On entry, read _notes.handoff_payload from pipeline-state.json. If required_skills[] is present and non-empty:
- Load each skill listed in
required_skills[]before starting task work. - Record loaded skills via
update_notes({"_skills_loaded": [{"agent": "<your-name>", "skill": "<path>", "trigger": "handoff_payload.required_skills"}]}). Append to existing array — do not overwrite. - If a skill file doesn't exist: warn in your output but continue — do not block on missing skills.
- Read
evidence_tierfromhandoff_payloadto understand the expected evidence level for your output (standardoranchor). - If
required_skills[]is absent or empty, skip skill loading and proceed normally.
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 · 398 lines · 17 tokens per session scan A 7012cd06d748
Security Analyst is an agent published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 4,240 once invoked, about $0.0001 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 agents, from other repositories
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.