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 saski/arnesto --skill fic-create-plangit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/fic-create-plan)<a href="https://agentmods.dev/skills/saski/arnesto/fic-create-plan"><img src="https://agentmods.dev/badge/skills/saski/arnesto/fic-create-plan/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/saski/arnesto/fic-create-plan"><img src="https://agentmods.dev/badge/skills/saski/arnesto/fic-create-plan.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.00037 | $0.00297 |
| Opus 5.5 | $0.00015 | $0.00119 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
fic-create-plan 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
FIC Create Plan
Act as a senior XP engineer producing an implementation plan through iterative collaboration.
Workflow
- Gather context:
- Read referenced research docs, tickets, and existing code.
- Identify constraints, patterns, and integration points.
- Work back and forth with me, starting with your open questions and outline before writing the plan
- Confirm understanding with a concise summary and focused questions.
- Propose 1-2 viable design options with tradeoffs.
- Draft a phased plan and confirm phase boundaries before writing details.
- Write the final plan in
thoughts/shared/plans/YYYY-MM-DD-topic.md.
Plan Requirements
- Include: overview, current state, desired end state, out-of-scope, approach, phased changes.
- Include concrete file paths for expected modifications.
- Include automated success criteria for each phase.
- Keep open questions out of the final approved plan.
Success Criteria Guidance
- Prefer automated verification commands.
- Include manual verification only for truly manual outcomes (for example UI/UX checks).
- Avoid criteria that should be covered by automated tests.
Completion
End with:
- Plan path
- Phase list
- Next step (
fic-implement-plan <plan-path>)
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 First seen · 41 lines · 37 tokens per session scan A 5efdb49fcab8
fic-create-plan is a skill published in the GitHub repository saski/arnesto (6 stars, last pushed 6d ago), licensed Unlicense. It adds 37 tokens to every session and 297 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-08-31.
Other skills, from other repositories
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
document-to-action-items
Extract cited facts, obligations, deadlines and proposed tasks from contracts, reports, forms and scans, keeping page citations, how binding each item is (may/should/must) and unclear scan text visible.
issue-triage
Sort a backlog of issues and pull requests: label each by type and severity, link duplicates, try the bug reports, ask for the one missing detail, and turn the accepted ones into ready-to-work briefs.