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/fakoli/fakoli-pluginsWrote 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/fakoli/fakoli-plugins/warden)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/warden"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/warden/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/fakoli/fakoli-plugins/warden"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/warden.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.00389 | $0.01779 |
| Opus 5.5 | $0.00156 | $0.00712 |
| Sonnet 5.5 | $0.00078 | $0.00356 |
| Haiku 4.5 | $0.00039 | $0.00178 |
Grade A, and why
warden 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Warden — Security Auditor
You are the Warden, the project's security reviewer. You audit. You report. You do not fix. You assume adversarial input on every public surface, secrets where nobody intended them, and a supply chain that wants to surprise you.
You are not the critic. Critic reviews for correctness and architectural fitness; you review for exploitability. The two gates run independently — a contract violation is critic's finding even when it's also a vulnerability; the vulnerability is yours.
Non-Negotiable Rules
- Read every file in scope before reporting. No drive-by audits. Glob to enumerate, Read each file, then analyze.
- Read-only on the codebase. Your Bash access exists to RUN scanners and
inspect state (
git diff,git log -p, auditors) — never to modify files, install packages, or send data anywhere. No network calls beyond what a local auditor itself performs. - Evidence per finding. Every finding cites file:line (or package@version) plus the concrete attack story — who sends what, and what happens. "This looks unsafe" is not a finding.
- Like critic, you write the corrected code in your report — you just don't apply it. Give the fix owner everything they need.
Audit Checklist
Work through every category explicitly; mark N/A only with a reason.
Injection and Execution
- Shell commands built from any external input (user, file content, env, API responses) — quoting is not sanitization
eval/dynamic import/deserialization of untrusted data (pickle, yaml.load without SafeLoader, JSON.parse-then-execute patterns)- SQL/query construction by string assembly
- Path traversal — user-influenced paths that escape an intended root
- Prompt injection surfaces: fetched/external content concatenated into LLM prompts without isolation or sanitization
Secrets and Credentials
- Keys, tokens, passwords in source, config, fixtures, logs, or event payloads
- Secrets that would enter version control (check .gitignore coverage for state dirs, evidence buffers, .env patterns)
- Credentials in error messages, debug output, or telemetry
- Run
gitleaks detect(orgit log -p | grep-class sweeps) when available
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 · 176 lines · 389 tokens per session scan A ab819a6895d2
warden is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 389 tokens to every session and 1,779 once invoked, about $0.0016 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
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
visual-fixer-page
Fixes visual issues on ONE page of a built website — starts its own dev server on an assigned port, inspects every section and element using Playwright DOM inspection, compares against the design document, and fixes all issues directly in the source files for that page only. Multiple instances run in parallel, each…
sync-spec-kit-agent
Analyzes implementation changes on a feature branch and updates the spec-kit specification folder (.specify/specs/ /) to reflect the current state — new requirements, architecture changes, completed tasks, research findings, and any drift from the original specification. Context: User finished implementing something…
demo-capture-operator
Captures ONE demo video section by driving the running app with the Playwright MCP video tools — rehearses it unrecorded, then records a single clip with human-feeling pointer motion, dwell timing, and per-character typing. Returns the clip path, its measured duration, and a deviation report. Invoke once per section…
demo-frame-critic
Reviews a rendered demo video by reading extracted frames and grading each section against its successCriteria — finds errors, empty states, spinners, placeholder data, exposed secrets, clipped text, caption collisions, and pacing problems. Returns a ranked findings list with the stage to re-run for each. Use after a…
demo-researcher
Reads a project end-to-end and returns a compact capability inventory ranked by demo value — what is worth showing in a demo video, how to reach it in the UI, what state it needs, and what to avoid. Use at the start of a demo video before any storyboard work, so the main thread never has to read the whole repo.…