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/claimnpx skills add fakoli/fakoli-plugins --skill claimgit 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/claim)<a href="https://agentmods.dev/skills/fakoli/fakoli-plugins/claim"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/claim.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.00051 | $0.04734 |
| Opus 5 | $0.00026 | $0.02367 |
| Sonnet 5 | $0.00010 | $0.00947 |
| Haiku 4.5 | $0.00005 | $0.00473 |
Grade A, and why
claim 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 — 322 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claim — Acquire an Exclusive Lease
Turn a ready task into an active claim: a row in state.db with a 60-minute lease, a branch checked out, and hooks watching every file touch. This is the entry point to the agentic execution loop. Nothing moves to claimed without going through here.
When to Use
- Starting work on a task after
/fakoli-state:planhas produced a ready queue. - When
fakoli-flow:executedispatches an agent against a fakoli-state task — the claim step happens inside that dispatch. - When
fakoli-crew:welderpicks up integration work, orfakoli-crew:scoutpicks up a research task — both land here before touching files. - When resuming after an interrupted session — check
fakoli-state statusfirst, then re-claim if the previous lease has expired and the task returned toready. - When coordinating parallel agents — each agent claims a separate task;
claimenforces the conflict gate.
Do not use this skill to inspect the queue without taking work — use /fakoli-state:state-ops for that. Do not use this skill to submit completed work — that is the Phase 5 finish skill.
Prerequisites
.fakoli-state/state.db must exist and the PRD must be in reviewed or approved status. Confirm before proceeding:
fakoli-state status
Look for prd-status: approved. The claim gate enforces this — fakoli-state claim raises ClaimError when prd-status is draft or none. If the PRD is not approved, proceed to /fakoli-state:prd first.
Phase 4 commands used in this skill:
| Command | Phase | Status |
|---|---|---|
fakoli-state next |
Phase 4 | available |
fakoli-state claim TASK_ID |
Phase 4 | available |
fakoli-state release CLAIM_ID |
Phase 4 | available |
fakoli-state renew CLAIM_ID |
Phase 4 | available |
fakoli-state show TASK_ID |
Phase 3 | available |
fakoli-state list --status ready |
Phase 3 | available |
Git is optional. When a git repo is present in the project root, claim automatically creates the branch agent/<task_id_lower>-<slug>. Without git, claim still succeeds — the record is written to state.db and the branch field is left null.
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 · 322 lines · 51 tokens per session scan A cb7e5ecd22f3
claim is a skill published in the GitHub repository fakoli/fakoli-plugins (4 stars, last pushed 28d ago), licensed MIT. It adds 51 tokens to every session and 4,734 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
jira-delivery
Close the needs-fix branch for both ticket classes: isolated git worktree, a red test BEFORE any implementation on change tickets, delegation to a core executor, every publish action (push / PR / comment / QA transition) gated behind a green @verification-agent verdict, commit + push + PR, then writeback via…
commit-message
Use ANY time the user signals they want to commit staged changes — including bare "commit", "/commit", "commit this", "commit these changes", "let's commit", "make a commit", "git commit", "write a commit message", "make a conventional commit", "use conventional commits", or any equivalent phrasing in context (e.g.…
git-commit
Generate conventional commit messages when staging files for commit in any of the project's repos. Do not use for git tag messages, merge commit messages, changelog entries, or automated version bump commits.
pr-generator
Use this skill when creating a pull request — generate the title, structured description, and review checklist from the branch's actual commits and diff. Don't use it for commit messages (git-commit skill) or changelogs.
ship
Review, fix, and commit in one run, with a gate before each phase.
commit-push
Use when asked to ship/publish commits without opening a PR.