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 skills/fakoli/fakoli-plugins/quicknpx skills add fakoli/fakoli-plugins --skill quickgit clone --depth 1 https://github.com/fakoli/fakoli-pluginsWhat 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 | $0.00016 | $0.01674 |
| Opus 5 | $0.00008 | $0.00837 |
| Sonnet 5 | $0.00003 | $0.00335 |
| Haiku 4.5 | $0.00002 | $0.00167 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 2d 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,674 once invoked, about $0.0001 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 skills, from other repositories
deno-knowledge-patch
Use this skill when choosing current Deno runtime APIs, CLI options, configuration, dependency behavior, Node compatibility, or deployment workflows. Open the topic reference before changing a project because several commands, flags, APIs, and defaults changed more than once.
agopengps-knowledge-patch
Use this skill when designing, extending, deploying, or diagnosing AgOpenGPS, AgIO, AgValoniaGPS, AgOpenWeb, GNSS correction paths, autosteer hardware, or machine-control hardware. Start by identifying the exact application release, codebase, board revision, firmware source commit, and operating mode.
apache-kafka-knowledge-patch
Use this skill when upgrading, configuring, extending, or operating Apache Kafka and its clients, Kafka Streams, Kafka Connect, MirrorMaker, KRaft, share groups, or tiered storage. Inspect the project's actual broker, client, metadata, and Java versions before applying version-dependent advice.
authjs-knowledge-patch
Use this patch to choose the maintained authentication path, avoid security-sensitive provider mistakes, and apply current Auth.js integration patterns. Read the topic reference before changing an affected flow; the quick reference prioritizes breaking behavior, security updates, and common implementation work.
centos-stream-knowledge-patch
Enterprise Linux 7 -> 8 -> 9 Enterprise Linux 8.10 -> 9.8 Enterprise Linux 9.8 -> 10.2.
clerk-knowledge-patch
Use this guide when implementing, upgrading, or debugging Clerk authentication, authorization, Organizations, Billing, SDKs, components, or deployment architecture. Start with the migration notes, then open the matching reference.