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 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/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/claim"><img src="https://agentmods.dev/badge/skills/fakoli/fakoli-plugins/claim.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.00022 | $0.00380 |
| Opus 5.5 | $0.00009 | $0.00152 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
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 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
Claim
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.
- Inspect
status,nextandshow TASK_ID. Check approved PRD status, ready task status, dependencies, acceptance criteria and overlapping file scope. - Run
claim TASK_ID --actor ACTOR(add--worktreewhen isolated git work is appropriate). Read the returned claim ID, branch/worktree and lease expiry. Task IDs and claim IDs are different identifiers. - Work only within the claimed scope. Renew with
renew CLAIM_ID --actor ACTORbefore the reported lease expires; use the host's supported scheduling or execution loop rather than promising an unstarted background timer. - For completed work, use the execute skill to submit evidence. To relinquish unfinished work, run
release CLAIM_ID --actor ACTOR --reason REASON.
Never steal another live claim with --force merely to unblock yourself. Coordinate shared files through the available agent mechanism; do not assume any named crew agent exists. Expired claims cannot be renewed retroactively: inspect current state and reacquire ownership before resuming.
CLI --help is authoritative for lease and actor flags. Hooks are supplementary: check their actual availability before relying on automatic file tracking.
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 · -302 lines · -29 tokens per session f6ec6f820e9a
- 1mo 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 22 tokens to every session and 380 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
issues-workflow
Plan and track work using a GitHub Issues-first workflow with sub-issue hierarchies, issue-branch-PR lifecycle, and auto-close on merge.
workspace-standards
Use when setting up or managing multi-repo workspaces.
omh-github-issue-intake
This is an OMH github-issue-intake workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
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).
github-workflow
GitHub best practices for pull requests, code reviews, issues, Actions workflows, and repository management.
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.