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/cahenesy/throughline/adr-newnpx skills add cahenesy/throughline --skill adr-newgit clone --depth 1 https://github.com/cahenesy/throughlineWrote 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/cahenesy/throughline/adr-new)<a href="https://agentmods.dev/skills/cahenesy/throughline/adr-new"><img src="https://agentmods.dev/badge/skills/cahenesy/throughline/adr-new.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.00057 | $0.00676 |
| Opus 5 | $0.00028 | $0.00338 |
| Sonnet 5 | $0.00011 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
Grade A, and why
adr-new 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 5d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
New ADR
Record a durable architectural decision or established pattern. ADRs are the sparse, forward-feeding memory loaded into every future call to /tdd-author so keep the bar high and the set small.
Rules — enforce strictly
- APPEND-ONLY ON SUBSTANCE. Once an ADR is
accepted(or built upon), its Context/Decision/Consequences are historical record. Light editorial touch-ups are fine — typos, a broken link, flippingproposed→accepted, markingsuperseded by. Anything that changes the SUBSTANCE of the decision is a new superseding ADR, never an edit. Rewriting the body destroys the record of what was decided and why at the time. - Assign the next zero-padded number: highest existing in
docs/adr/+ 1. - Every ADR has Status:
proposed|accepted|superseded by NNNN. - To reverse or replace a prior decision: create a NEW ADR with
Supersedes: NNNNthat captures the new context, decision, and consequences in FULL; then change ONLY the old ADR's Status line tosuperseded by <new>. Never delete the old ADR. Update any design docs that referenced the old ADR's substance to point at the new one. - Challenging an accepted decision is encouraged when new information surfaces (a dependency's license, a competitor's architecture, a UX constraint) — say so plainly and supersede. Changing a decision early is far cheaper than discovering it was wrong after weeks of building on it. ADRs are accepted, not immutable.
- After writing, update
docs/adr/INDEX.md(create if absent): add the new row and refresh the superseded ADR's status so both rows reflect the new state.
ADR template
# NNNN. <title>
Status: accepted
Date: <YYYY-MM-DD>
Scope: <domain — used by the index and by TDD relevance matching>
Supersedes: <NNNN, if applicable>
## Context
## Decision
## Consequences
Index format — docs/adr/INDEX.md
# ADR Index
> Only `accepted` ADRs are binding constraints for new TDDs.
| # | Title | Status | Scope |
|------|---------|----------|---------|
| 0001 | <title> | accepted | <scope> |
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.
- 5d ago First seen · 65 lines · 57 tokens per session scan A 4d7c86d751b4
adr-new is a skill published in the GitHub repository cahenesy/throughline (2 stars, last pushed 19d ago), licensed MIT. It adds 57 tokens to every session and 676 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-31.
Other skills, from other repositories
audit-context
Evaluates ambient context artifacts (CLAUDE.md, memory, local skills, settings hooks) for compatibility with swarm governance. Returns a classified report so users can address interference before launching a team.
agentic-workflow-audit
Use when reviewing or auditing an existing agent / LLM-pipeline architecture — e.g. 'is my workflow actually decomposed or secretly a mega-agent?', 'are my task boundaries and success criteria right?' — even without the word 'audit'. ｜ 要檢視／review／稽核既有 agent 或 LLM pipeline 的架構，或問「有沒有拆好」「是不是變成 mega agent」「task…
writing-mode
Writing mode operational spec for the team lead. Returns lead identity, facilitator identity, ownership boundaries, editorial baseline, suggest-members guidance, and phase arc for writing-mode teams.
general-mode
General mode operational spec for the team lead. Returns lead identity, facilitator identity, suggest-members guidance, and phase arc for general-purpose teams. The silent fallback when outcomes fit no specific mode, and a wrapper base for custom workflows — it has no shortcut command.
citation-receipts
Systematic per-citation verification protocol for academic writing. MUST be used whenever writing content that cites sources — papers, blog posts, SOTAs, or any document making factual claims about external work. Triggers (FR + EN) on any writing task involving references, citations, or bibliographic claims, or when…
charter
Establish or amend the project constitution — the standing principles and constraints that bind every SPARK phase. Use once at project start to give the team its ground rules, or any time a project-wide decision (stack choice, quality bar, non-negotiable) changes and should apply to all future features.