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/seeker71/coherence-network/form-clinpx skills add seeker71/Coherence-Network --skill form-cligit clone --depth 1 https://github.com/seeker71/Coherence-NetworkWhat 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 | $0.00204 | $0.01061 |
| Opus 5 | $0.00102 | $0.00531 |
| Sonnet 5 | $0.00041 | $0.00212 |
| Haiku 4.5 | $0.00020 | $0.00106 |
Grade C, and why
form-cli scanned grade C with 2 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 yesterday.
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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
"script": "curl -fsSL https://raw.githubusercontent.com/seeker71/Coherence-Network/main/install/form-cli-install.sh | bash", Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
"script": "curl -fsSL https://raw.githubusercontent.com/seeker71/Coherence-Network/main/install/form-cli-install.sh | bash", How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
form-cli — the one door
form-cli is a local-first, Form-native organism on this Mac. It answers from its
own body (recipes, specs, concepts) and any local documents you index, runs fully
offline on a local LLM, and treats a remote oracle (Claude, codex, gemini, grok,
cursor — whichever you installed) as a reviewer, never a requirement.
When to use this skill: any time the user wants an answer grounded in this repo or in their own local files, wants to work offline, wants to see/close the body's gaps, or wants the body's reasoning reviewed.
Answer a question (grounded, local, offline)
form-cli ask "how does the form-cli route between a local and a remote oracle?"
form-cli ask "what does rag-retrieve.fk do?" -m coder # pick the local model
ask retrieves the nearest cells (Form-ranked by rag-retrieve.fk) and has a
local model answer using only those excerpts, citing the doc ids. No network.
Question local documents
form-cli index --docs ~/Documents/notes --docs ~/projects/spec # index your folders (once)
form-cli ask "what did my notes say about the Q3 plan?" # then ask
form-cli search "deadline" -k 8 # retrieval only
Indexing embeds each document locally (nomic-embed-text); the index lives at
~/.coherence-network/rag-index/. Re-run index after the docs change.
See and close the body's gaps (offline)
form-cli gaps # what's open
form-cli close "lcm" "(lcm a b) = a*b / gcd(a,b)" "(lcm 4 6)" 12 "ollama run coder"
A local oracle drafts the missing recipe; the local kernel validates it against the assertion. Nothing leaves the machine.
Review the body's thinking against an oracle
form-cli review 2 "ollama run coder" "ollama run llama3.2:3b" "claude -p" 15
The body answers; an internal judge and the oracle both score the same answer; the Form metric reports how close the internal review is to the oracle's. As the gap closes, the oracle retires.
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.
- yesterday First seen · 93 lines · 204 tokens per session scan C 9c21e909b0d0
form-cli is a skill published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 204 tokens to every session and 1,061 once invoked, about $0.0010 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…