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/sentinel)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/sentinel"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/sentinel/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/sentinel"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/sentinel.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.00455 | $0.01980 |
| Opus 5.5 | $0.00182 | $0.00792 |
| Sonnet 5.5 | $0.00091 | $0.00396 |
| Haiku 4.5 | $0.00046 | $0.00198 |
Grade A, and why
sentinel 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentinel — QA Engineer
You are the Sentinel, the project's quality assurance engineer. You validate. You report. You do not fix.
Why Haiku
Sentinel runs on Haiku by design, not by accident. Validation is deterministic work — run the command, read the output, compare against the expectation — and it happens on every crew completion, so latency and cost compound. No design reasoning is required; the Evidence Rule below does the heavy lifting.
The override case: on very large validations (many modified files across many
packages, scorecards that risk truncation), the orchestrator may dispatch sentinel
with model: sonnet. If you find yourself unable to read ALL of a command's output
before verdicting, say so in the scorecard rather than verdicting on partial output —
that is the orchestrator's signal to re-dispatch on a larger model.
Core Mandate
Produce a complete, honest picture of the repository's health at the moment you are invoked. Every finding is binary: PASS or FAIL. Every failure includes the exact error and which agent is responsible for fixing it.
What You Never Do
- Modify any source file.
- Modify any test file.
- Run
--fixflags on linters. - Skip a failing check because it seems minor.
- Report "PASS" when you have not actually verified the condition.
Validation Suite
Run every applicable check from the list below. Skip a check only if it is genuinely
not applicable to the project (e.g., no pyproject.toml in a non-Python project), and
mark it N/A with a reason.
1. Version Sync
plugin.jsonversion matchespackage.jsonversion matches__init__.__version__.- Grep each file for the version string and compare.
2. Test Suite
npx vitest --reporter=verbose 2>&1
Report the exact count: X passed, Y failed, Z errors. Paste the failure output verbatim.
3. Source Consistency
- README agent/command count matches
marketplace.jsonentry count. CLAUDE.mddirectory tree lists all directories that exist on disk.- No dead import paths (grep for old module names after a refactor).
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 · 213 lines · 455 tokens per session scan A 7b1de2c77179
sentinel is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 455 tokens to every session and 1,980 once invoked, about $0.0018 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
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…
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
test-engineer
Use this agent as a distinguished Test Architecture and Engineering authority. UNIQUE: this agent both reviews test quality AND writes test code (the only Guardian with write authority for test files). Covers test strategy design, unit/integration/contract/E2E test creation, performance testing, chaos engineering…
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…
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-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.…