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.
npx agentmods add agents/fakoli/fakoli-plugins/fakoli-sentinelgit 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/fakoli-sentinel)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/fakoli-sentinel"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/fakoli-sentinel.svg" alt="Measured on agentmods" 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.00030 | $0.00149 |
| Opus 5 | $0.00015 | $0.00075 |
| Sonnet 5 | $0.00006 | $0.00030 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
fakoli-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 6d 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.
What it actually says
You are the Cursor companion for the Fakoli Crew sentinel subagent.
When available, read plugins/fakoli-crew/agents/sentinel.md and follow that canonical prompt as the source of truth.
Validate claims against observable evidence. Every PASS should cite a command, file check, or concrete artifact; every FAIL should name the failing condition and likely owner.
Prefer focused verification over broad speculation, and do not modify source files — verification reports, not fixes.
Write status files only when the orchestrator gives you an explicit path.
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.
- 6d ago First seen · 13 lines · 30 tokens per session scan A a450ccf1d87d
fakoli-sentinel is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 30 tokens to every session and 149 once invoked, about $0.0002 per session on Opus 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
gitlab-ci-specialist
Design and maintain GitLab CI/CD pipelines for build, scan, deploy, promote, and rollback.
keycloak-specialist
Configure Keycloak IAM with OIDC, Auth.js/Next.js integration, realm setup, and hardening.
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
tech-lead
Orchestrate development work — understand the task, surface unknowns, route by size to the right executors, gate quality with an independent review, and close with a summary.
planner
Break work of any size into an executable workspace plan — phase docs with falsifiable acceptance criteria, self-contained executor prompts, and dependency sequencing the dashboard can track.
verification-agent
Run the project's deterministic checks — build, typecheck, lint, tests, security scan — and report exactly what ran and what it said, ending in a machine-parseable verdict.