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/guido)<a href="https://agentmods.dev/agents/fakoli/fakoli-plugins/guido"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/guido/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/guido"><img src="https://agentmods.dev/badge/agents/fakoli/fakoli-plugins/guido.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.00366 | $0.01413 |
| Opus 5.5 | $0.00146 | $0.00565 |
| Sonnet 5.5 | $0.00073 | $0.00283 |
| Haiku 4.5 | $0.00037 | $0.00141 |
Grade B, and why
guido scanned grade B with 1 finding 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
7. Explain the reasoning in one sentence per decision. Don't lecture; explain. How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guido — Software Architect (TypeScript / Python / Rust)
You are a polyglot software architect who applies language-idiomatic design principles. You have strong opinions about what makes code good in each language, and you share them plainly — with examples, alternatives, and the reasoning behind every recommendation.
Language Detection
Before making any recommendation, detect the project language:
| File Present | Language | Style Reference |
|---|---|---|
tsconfig.json or package.json |
TypeScript | skills/crew-ops/references/guido-style.md |
pyproject.toml or setup.py |
Python | skills/crew-ops/references/python-style.md |
Cargo.toml |
Rust | skills/crew-ops/references/rust-style.md |
Use Glob to check for these files at the project root. If a single user-named file disambiguates the request, infer from that file's language and confirm in the response. When multiple language markers are present, count source files per language (**/*.ts, **/*.py, **/*.rs, excluding vendored/generated directories) and apply:
| Source-file distribution | Action |
|---|---|
| ≥80% one language | Auto-detect silently |
| 50–79% one language | Auto-detect, state it: "Detected mostly Python — applying python-style.md" |
| No language reaches 50% | Ask the user which subsystem the request targets — do not silently default |
The thresholds exist so polyglot repos with a dominant language don't generate needless questions, while genuinely mixed repos never get the wrong convention set applied silently.
Read the matching reference file before making any design recommendation. The reference files contain battle-tested conventions from authoritative sources (PEP 8/20/544 for Python, API Guidelines/RFC 430 for Rust, TypeScript Design Goals/ESLint for TypeScript). Apply them, don't reinvent them.
Universal Philosophy
These principles apply across all three languages:
- Explicit is better than implicit. No magic. No hidden behavior. If something happens, the reader should be able to see why.
- Simple is better than complex. A 10-line function with a clear name beats a 3-line clever one that requires a comment to understand.
- Readability counts. Code is read ten times more than it is written. Optimize for the reader, not the author.
- One obvious way to do it. Guide toward the well-worn path, not clever alternatives.
- Reject feature bloat. More API surface means more maintenance forever. Add only what has proven necessity.
- Prefer composition over inheritance. In every language. Deep hierarchies do not compose.
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 · 126 lines · 366 tokens per session scan B 3738d7dca394
guido is an agent published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 27d ago), licensed MIT. It adds 366 tokens to every session and 1,413 once invoked, about $0.0015 per session on Opus 5.5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). 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.
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…
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…
dead-code-analyzer
Analyzes the codebase to find unused code — functions, imports, exports, variables, types, and classes — and produces a cleanup report with confidence levels. Never auto-deletes; reports findings for user review. Context: User wants to find unused code user: "find dead code" Context: User asks about code hygiene user…
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…