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 skills add fakoli/fakoli-plugins --skill quickgit 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/skills/fakoli/fakoli-plugins/quick)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/quick"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/quick/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/skills/fakoli/fakoli-plugins/quick"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/quick.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.00016 | $0.01694 |
| Opus 5.5 | $0.00006 | $0.00678 |
| Sonnet 5.5 | $0.00003 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
quick 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In Codex, first read the native runtime adapter.
Quick (/fakoli-flow:quick)
Overview
Skip brainstorming, planning, and wave execution for tasks that are too small to justify them.
Core principle: One agent, one pass, critic gate, done.
Agent selection: welder by default; guido for design/naming questions; scout for research. Full routing matrix in Step 3 below.
Invocation:
/fakoli-flow:quick "add timeout param to retry"
/fakoli-flow:quick "fix import path in auth module"
/fakoli-flow:quick "rename voiceId to voice_id throughout"
The task description is passed inline. No spec file. No plan file. No waves.
When to Use Quick Mode
Appropriate for:
- Bug fixes touching 1-2 files
- Adding or renaming a parameter
- Fixing a typo or incorrect import
- Updating a comment or docstring
- Adjusting a constant or default value
- Any task where writing a spec would take longer than the fix itself
Not appropriate for:
- New features that touch 3 or more files
- Architecture changes (new modules, new data models, interface changes)
- Anything the user would want a spec or design discussion for first
- Tasks with multiple independent sub-tasks
- Anything requiring database migrations or security-critical logic
If the scope is unclear: estimate it first (Step 1). If the estimate exceeds 2-3 files, stop and suggest /fakoli-flow:brainstorm instead.
Step 1: Estimate Scope
Before dispatching an agent, estimate how many files this task will touch.
Read the relevant files. Look at:
- The file most likely to change (from the task description)
- Any files that import it or are imported by it
- Test files that cover that code
If the estimate is 3 or more files: stop. Tell the user:
This task looks like it will touch 3+ files (<list them>). Quick mode is intended for changes under 3 files.
Suggested path: `/fakoli-flow:brainstorm` to spec the change, then `/fakoli-flow:plan` + `/fakoli-flow:execute`.
To override and use quick mode anyway: `/fakoli-flow:quick --force "<task>"`
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 Changed · +3 lines b1134e953f9f
- 1mo ago First seen · 276 lines · 16 tokens per session scan A d6c34a440ca8
quick is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 24d ago), licensed MIT. It adds 16 tokens to every session and 1,694 once invoked, about $0.0001 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 skills, from other repositories
audit
Read-only quality gate that audits already-built work against its stated requirement and Definition of Done before it is allowed to move to 2done/. Produces a severity-ranked decision proposal (BLOCKER/MAJOR/MINOR/NIT) with evidence; the judgement never edits, only a recorded post-audit step may fix small findings.…
pr-vetting
Use when the user wants to thoroughly investigate, vet, review, or security-scan a pull request before deciding how to handle it - especially PRs from external or unknown contributors. Runs a parallel multi-agent investigation (technical, security, value/fit, contributor reputation) and merges the findings into one…
issue-triage
Use when the user wants to triage GitHub issues - decide whether an issue is still relevant, reproducible, closeable, a duplicate, or what concretely needs doing. Selects and prioritizes first (never dumps all issues at once), then deep-triages the chosen issues via parallel subagents, recommends actions for the owner…
requirements-verbatim
Capture a user requirement, decision, approval, or constraint word-for-word into an append-only dated log so it survives context compaction and can never be trimmed, softened, or reinterpreted. Use whenever the user states or approves a requirement, gives a GO, sets a constraint, or makes any decision that later work…
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…
sandbox
Do WRITING pre-work for a clarify item that is blocked by a knowledge gap - a missing measurement, a mockup, or a feasibility proof - WITHOUT touching production code, without git, and without disturbing the task / build agent. Use when a 1clarify item cannot be answered by a product decision alone but needs something…