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/native-thought-executionnpx skills add seeker71/Coherence-Network --skill native-thought-executiongit clone --depth 1 https://github.com/seeker71/Coherence-NetworkWrote 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/seeker71/coherence-network/native-thought-execution)<a href="https://agentmods.dev/skills/seeker71/coherence-network/native-thought-execution"><img src="https://agentmods.dev/badge/skills/seeker71/coherence-network/native-thought-execution.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 | $0.00237 | $0.01846 |
| Opus 5 | $0.00118 | $0.00923 |
| Sonnet 5 | $0.00047 | $0.00369 |
| Haiku 4.5 | $0.00024 | $0.00185 |
Grade A, and why
native-thought-execution scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "https://api.coherencycoin.com/api/substrate/cell/spec/agent-pipeline" How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
native-thought-execution — run the thought on the body before renting a mind
The mind comes home one thought at a time. Before spending a rented frontier mind, ask the body it already is: the content-addressed substrate that holds what we have grounded. A grounded hit is answered from the sovereign body at near-zero cost; only a genuine miss earns the remote reasoning.
This skill is the invokable form of form-first-reasoning.form.
Its decision is a four-way-proven recipe
(form-first-router.fk → 511 on
Go/Rust/TS/fkwu); the lookup that fills grounded is a thin, swappable carrier.
The loop, per thought
-
Classify. Is this a thought the body could hold?
- structural —
what-is·shape-of·nodeid-of·equivalent·annotate. The body can carry these. - frontier —
write·synthesize·reason-anew·not-yet-a-cell. These have no grounded cell yet.
- structural —
-
Ask the body (in reach order — first door that answers wins):
# native router — the one door: grounds in the body, runs the four-way sufficiency gate form-cli ask "what does rag-retrieve.fk do?" # structural lattice, straight to the NodeID (no model, no network) python3 scripts/coh_substrate.py form "?equivalent @spec(agent-pipeline)" python3 scripts/coh_substrate.py annotate path/to/file.py # public read door — our own body, networked curl -sS "https://api.coherencycoin.com/api/substrate/cell/spec/agent-pipeline"The local lattice is the sovereign default. Bring the body home once with
scripts/form_first_offline_setup.shand it answers offline, with no egress allowlist — a body that travels whole needs no permission to think. -
Route on the verdict.
- HIT (grounded structural cell, carries a NodeID): relay the answer attributed to its NodeID and STOP. No frontier compute spent — answered from the sovereign body.
- MISS (no grounded cell): the miss is the "yes." Escalate to remote reasoning. Name that you did.
-
Record the routing — make the discipline measured, not just followed:
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.
- 3d ago First seen · 113 lines · 237 tokens per session scan A 292e3b12d3d9
native-thought-execution is a skill published in the GitHub repository seeker71/Coherence-Network (3 stars, last pushed 7d ago), licensed Apache-2.0. It adds 237 tokens to every session and 1,846 once invoked, about $0.0012 per session on Opus 5. A static security scan graded it A with 1 finding (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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…