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 state-opsgit 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/state-ops)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/state-ops"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/state-ops/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/state-ops"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/state-ops.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.00031 | $0.00444 |
| Opus 5.5 | $0.00012 | $0.00178 |
| Sonnet 5.5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
state-ops 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.
What it actually says
State Ops
Resolve this plugin's installed root from the loaded skill path. Prefer its bin/fakoli-state launcher when no matching CLI is on PATH; run from the user's project or pass the command's --cwd argument. Read --help when a flag is uncertain. Use only tools exposed by the current host. For native MCP calls, supply the target project's absolute cwd; the server's startup directory is the installed package.
- Resolve the project directory and verify
.fakoli-state/state.dbexists. If absent, report an uninitialized project; runinitonly when project setup is part of the request. - Run
fakoli-state status, then uselist --status ready,list --status in_progress,show TASK_ID, ornextto answer the actual question. Use--cwd PROJECTwhen the shell is elsewhere.nextselects work without claiming it. - Inspect task dependencies and claim scope before recommending work. For local filesystem/git discrepancies, run bare
fakoli-state syncand read its report.sync --fixchanges state; provider sync may write remote issues. Execute those only within the requested remediation scope. - Report concrete task IDs, claim/blocker evidence and the next available action. For machine summaries, use
status --hook-format; do not parse the decorative human output.
The current CLI has no conflicts or decision top-level command. Use the actual exposed MCP conflict tool if available, or inspect show/claim scope and local sync output. Some inspection commands initialize storage or reap expired leases: do not describe them as byte-preserving reads. Never repair canonical state by editing SQLite directly.
See GitHub sync before any provider operation. A local status request does not authorize a remote push or a recurring watcher.
See README for setup and the full CLI/MCP surfaces.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · -308 lines · -32 tokens per session de16fcf69ee8
- 1mo ago First seen · 328 lines · 63 tokens per session scan A fe79928eeaf7
state-ops is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 31 tokens to every session and 444 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-09-03.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
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…
monorepo-coordination
Coordinate changes spanning 2+ repos of a multi-repo workspace or 2+ apps/packages of a monorepo -- merge-order plans, MR/PR templates, post-merge checklists. NOT for single-repo changes, even large ones.