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 finna/Finn-loop --skill finn-buildgit 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-build)<a href="https://agentmods.dev/skills/finna/finn-loop/finn-build"><img src="https://agentmods.dev/badge/skills/finna/finn-loop/finn-build.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.00057 | $0.01198 |
| Opus 5 | $0.00028 | $0.00599 |
| Sonnet 5 | $0.00011 | $0.00240 |
| Haiku 4.5 | $0.00006 | $0.00120 |
Grade A, and why
finn-build 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 7d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Finn-loop builder
One pass = one unit of work: fix review feedback on one existing PR, or build
one issue end to end. Under /loop, each iteration runs this skill once.
0. Preflight
Before changing Linear, GitHub, branches, or files:
- Confirm this is the intended GitHub repository and
originis reachable. - Detect the repository's default branch with
gh repo view --json defaultBranchRef --jq .defaultBranchRef.name; never assume it ismain. - Require a clean working tree (
git status --porcelainmust be empty). If it is dirty, report the paths and end the pass. Never stash, reset, overwrite, or commit unrelated work.
1. Review feedback first
List open PRs labeled loop-changes-requested, including their labels:
gh pr list --state open --label loop-changes-requested --json number,title,headRefName,headRefOid,labels,updatedAt,url
Skip every PR carrying needs-human-review; it has left the automated repair
queue until a human resolves the escalation.
If any PR remains, choose the least recently updated one. Read its linked
Linear issue and latest Finn-loop review of COMMIT_SHA verdict. Check out its
branch, fix only the "Must fix before merge" items, run the relevant checks,
push, remove loop-changes-requested, and comment with what changed. End this
pass.
If a proposed fix would cross an issue non-goal or requires a product decision,
do not implement it. Comment the exact conflict, add needs-human-review,
remove loop-changes-requested, and end the pass. This prevents the next loop
iteration from retrying a decision only a human can make.
2. Pick
Using the Linear connector, list issues on team TEAM that meet every
condition:
- labeled
agent-ready - unassigned
- not labeled
blocked - no unresolved blocker relation
Sort by priority, then oldest first. If the queue is empty, say so and end the pass. Do not invent work and do not pick a blocked issue.
3. Claim (the cooperative lock)
Assign yourself and move the issue to the team's started workflow state
(prefer In Progress when available). Claim before reading deeply or writing
code. Re-fetch the issue immediately after the update; if it is blocked,
assigned to somebody else, or no longer agent-ready, do not work it and
return to step 2.
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.
- 7d ago First seen · 128 lines · 57 tokens per session scan A 7a0aadae953a
finn-build is a skill published in the GitHub repository finna/Finn-loop (305 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,198 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
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
repo-harness-product
Canonical rule owner for PRD drafting, Sprint planning/execution, and native Goal-session preparation from repo-harness planning artifacts.
linearis
Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user mentions Linear, a ticket identifier like…