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 fakoli/fakoli-pluginsnpx agentmods add plugins/fakoli/fakoli-plugins/fakoli-crewgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsGrade A, and why
fakoli-crew 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 2d 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
{
"name": "fakoli-crew",
"version": "2.9.2",
"description": "Nine specialist AI agents for software engineering — generalist roles (polyglot architect, code reviewer, security auditor, researcher, plugin engineer, integration specialist, documentation writer, infrastructure keeper, QA validator) with TDD enforcement, systematic debugging, and verification gates. Plugin-surface critics (agent/skill/hook/mcp/structure) moved to fakoli-plugin-critic in 2.3.0.",
"author": {
"name": "Sekou Doumbouya",
"url": "https://github.com/fakoli"
},
"repository": "https://github.com/fakoli/fakoli-plugins",
"license": "MIT",
"keywords": [
"agents",
"team",
"crew",
"orchestration",
"code-review",
"typescript",
"architecture",
"workflow"
]
}
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.
- 2d ago First seen · 22 lines scan A d3c3e9f08454
fakoli-crew is a plugin published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 24d 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
credo
The mentor framework for Claude Code: a self-contained process layer with per-session modes, a work-item lifecycle with a hard Definition of Done, budget-aware autonomy, visual verification, and safety rules that travel into every subagent.
dogma
Intelligent sync of Claude instructions with enforcement hooks for security and consistency.
get-shit-done
Installer for the Get-Shit-Done workflow system (own secured & frozen fork, markdown skills only) - meta-prompting, context engineering and spec-driven development.
claudit
Audit and optimize your Claude Code configuration. Caches current Claude Code ecosystem knowledge so any subsequent agent task — building a skill, configuring an MCP, authoring CLAUDE.md — can read it instead of re-fetching docs.
dev-workflow-forge
A generator kit for Claude Code dev tooling. Three skills read your codebase and write a project-specific review skill, a rules set, and a self-learning feedback loop tuned to your stack, instead of handing you tooling written for someone else's project.
fp-barbeque
Understanding-first mode: on exploratory tasks (refactors, design, ambiguous scope) the model grills you toward mutual understanding before it writes code, so you can debug and own the result. Sets a prior at the task edge; never steers mid-solve. Modes: off, on (default).