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/finna/finn-loop/finn-specnpx skills add finna/Finn-loop --skill finn-specgit clone --depth 1 https://github.com/finna/Finn-loopWrote 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/finna/finn-loop/finn-spec)<a href="https://agentmods.dev/skills/finna/finn-loop/finn-spec"><img src="https://agentmods.dev/badge/skills/finna/finn-loop/finn-spec.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.00056 | $0.00752 |
| Opus 5 | $0.00028 | $0.00376 |
| Sonnet 5 | $0.00011 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
finn-spec 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 6d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec interview
Turns a raw idea into a Linear issue so complete that a build agent needs nothing beyond the issue. Works like plan mode: research the codebase, interview the user in rounds until confident, draft, confirm, file. The user is the product brain; you are the codebase brain. Never guess product decisions.
1. Research before asking
Read the relevant code first. Find which files are involved, what patterns already exist, and what constraints apply. Never ask the user something the codebase can answer.
2. Interview in rounds
Ask 1-4 questions per round, each with concrete options and your recommended option first. Ask only genuine product decisions:
- Behavior forks: who sees it, what exactly happens, where does it live
- Scope boundaries: what is explicitly out of this issue
- Edge cases that change acceptance criteria: empty states, permissions, failure handling
- Data implications: existing records, migrations
After each round, fold the answers in and apply the confidence test:
Could two different engineers read this spec and ship the same observable behavior?
If any fork remains, ask another round. There is NO cap on rounds: a small fix might need two questions; a big feature legitimately needs 10-20+. Never stop early because it feels like a lot of questions. Once the test passes, stop — no filler questions.
3. Draft the issue
Use exactly this shape:
## Problem
What user or business problem does this solve? One or two sentences.
## Acceptance Criteria
- [ ] AC-1 — Observable, testable outcome one
- [ ] AC-2 — Observable, testable outcome two
## Non-goals
- NG-1 — What must NOT change in this task
- NG-2 — What is explicitly excluded or saved for later
## Relevant files
- path/to/file.ts — why it matters
## Test expectations
- What should be tested, manually or automatically
## How to verify
1. Numbered manual steps anyone can follow to confirm the work: where to
go, what to do, exactly what should happen. Cover every AC.
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.
- 6d ago First seen · 97 lines · 56 tokens per session scan A 47ce8b36d9d4
finn-spec is a skill published in the GitHub repository finna/Finn-loop (305 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 752 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-08-30.
Other skills, from other repositories
openclaw-github-repo-commander
7-stage super workflow for GitHub repo audit, cleanup, PR review, and competitor analysis.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
ultralytics-platform
This skill should be used when user asks to "upload my model to Ultralytics Platform", "push this run to the platform", "upload a dataset to platform", "download a dataset from platform", "search platform datasets", "start cloud training", "train on platform GPUs", "export a model on platform", "deploy a model…
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…