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/implement-statusnpx skills add cahenesy/throughline --skill implement-statusgit clone --depth 1 https://github.com/cahenesy/throughlineWhat 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.00099 | $0.01102 |
| Opus 5 | $0.00049 | $0.00551 |
| Sonnet 5 | $0.00020 | $0.00220 |
| Haiku 4.5 | $0.00010 | $0.00110 |
Grade A, and why
implement-status 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 2d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement status
A read-only progress view for the /build-tdds run. The runner
writes a structured run-state record under
docs/tdd/.implement-logs/<ts>/state.d/ (FR-27); this skill renders it.
What you see
The snapshot derives the rendered view fresh on each call from the per-TDD fragments — there is no second artifact that can drift from the record. It shows:
- Header — mode (sequential / combined / parallel), integration branch, elapsed time, run state.
- Rollup —
<completed> done / <total> · ~<P>% (estimate)— the percent is always suffixed(estimate)and never reads 100% while any TDD is non-terminal (FR-30 honesty). Failed / blocked / skipped counts are reported separately when non-zero. - Per-TDD table — queue position, slug, status
(
pending|building|verifying|reviewing|done|failed|blocked|skipped), current stage (build|test-first|verify|verify-runtime|review|flip), and the TDD's branch / PR URL when known. - Current focus — the in-progress TDD and its stage, when a TDD is non-terminal.
If no /build-tdds run is active, the skill says so plainly and (if a previous
run exists) summarizes the last run's final state. It never reports false
progress.
Halted runs
When the most recent run is halted (state paused, blocked, or failed), the
snapshot switches to a one-screen halt context (FR-64): the halt cause from the
closed enum, the triggering finding reference, and the deterministic next-action
options, each on its own numbered line. Halted-run rendering fits 24×80 by
default; to see full logs use cat docs/tdd/.implement-logs/<runid>/REPORT. The
Resume: /build-tdds --resume <runid> line appears only when the cause is a
recoverable (paused-state) one.
A run whose state is interrupted (TDD 0030 §3) did not exit cleanly — the
runner died mid-gate, leaving one or more TDDs orphaned in a non-terminal status.
The snapshot renders a distinct "the run did not exit cleanly" banner naming each
orphaned TDD + gate and pointing at /build-tdds --resume <runid>; it is never
reported as done.
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.
- 2d ago First seen · 92 lines · 99 tokens per session scan A a5ab0d140fb3
implement-status is a skill published in the GitHub repository cahenesy/throughline (2 stars, last pushed 16d ago), licensed MIT. It adds 99 tokens to every session and 1,102 once invoked, about $0.0005 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
agent-project-board-sync
Agent skill for project-board-sync - invoke with $agent-project-board-sync.
agent-issue-tracker
Agent skill for issue-tracker - invoke with $agent-issue-tracker.
agent-planner
Agent skill for planner - invoke with $agent-planner.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…