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/state-opsnpx 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.svg" alt="Measured on agentmods" 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.00063 | $0.03339 |
| Opus 5 | $0.00032 | $0.01670 |
| Sonnet 5 | $0.00013 | $0.00668 |
| Haiku 4.5 | $0.00006 | $0.00334 |
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 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
State-Ops — State Inspection
Read the canonical SQLite state that fakoli-state maintains: project summary, task inventory, claim activity, dependency graph, conflict warnings, and filesystem reconciliation. This skill makes no mutations.
When to Use
- When orienting before starting a work session — run
statusfirst, always. - Before claiming a task — confirm the PRD is approved and the task is
ready. - When a claim was interrupted and the state of the queue is unclear.
- When multiple agents are active and conflict risk is non-trivial.
- When a task shows as
blockedand the blocker chain needs tracing. - When suspicious that orphan branches or stale packets exist on disk.
- When reporting project progress to a human or another skill.
State-ops is NOT for authoring or reviewing PRDs — use the prd skill. State-ops is NOT for generating plans or scoring tasks — use the plan skill. State-ops is NOT for claiming work or submitting evidence — use the claim and execute skills. This skill only reads.
Prerequisites
The project must have run fakoli-state init at least once. Check for the sentinel file:
ls .fakoli-state/state.db 2>/dev/null || echo "MISSING: run fakoli-state init first"
If .fakoli-state/state.db does not exist, refuse to proceed and tell the caller to run:
fakoli-state init --name "<project-name>"
Do not attempt to read state, list tasks, or call any other fakoli-state command until state.db is confirmed present.
Workflow
Step 1 — Get the project summary
Phase 2 — available now.
fakoli-state status
Returns: PRD status (draft / reviewed / approved), total task count, per-status breakdown (proposed, drafted, reviewed, ready, claimed, in_progress, done), active claim count, blocker count, and sync state.
Run this first. The output orients every subsequent decision — it answers whether work is even possible before touching any other command.
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 · 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 63 tokens to every session and 3,339 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
better-auth-knowledge-patch
Use this skill when implementing, upgrading, debugging, or reviewing Better Auth applications. Start with the quick references below, then load the topic file that matches the task.
clickhouse-knowledge-patch
Use this skill when writing, reviewing, upgrading, or operating ClickHouse SQL and server configurations. Start with the compatibility-sensitive items below, then load the topic reference that matches the task.
arch-knowledge-patch
Restart the daemon immediately after upgrading openssh to 9.8p1 because the old daemon cannot accept new connections.
axum-knowledge-patch
Axum 0.8 uses return-position impl Trait in FromRequestParts and FromRequest. Implement their methods with native async fn; do not retain the old #[asynctrait] annotation.
caddy-knowledge-patch
Use this patch when writing or reviewing Caddyfile or JSON configuration, upgrading Caddy, building custom binaries, or operating Caddy's HTTP, proxy, certificate, and telemetry features.
cloudflare-d1-knowledge-patch
Use this skill when designing, implementing, migrating, operating, or debugging Cloudflare D1 databases. Check the project’s Wrangler configuration, binding usage, database generation, account plan, and remote-versus-local command flags before applying guidance.