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/outlinedriven/outline-driven-development/append-run-lognpx skills add OutlineDriven/outline-driven-development --skill append-run-loggit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/append-run-log)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/append-run-log"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/append-run-log.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.00063 | $0.01089 |
| Opus 5 | $0.00032 | $0.00544 |
| Sonnet 5 | $0.00013 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
append-run-log 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 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.
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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Append run log
Contract
| Field | Bound contract |
|---|---|
| Trigger | A completed agent run must be recorded as durable, queryable evidence. |
| Authority | Reversible local write to the run log only; prior entries are never rewritten. |
| Side effect | Appends one entry to the append-only JSONL run log under an ISO-only date guard, prunes entries older than the declared retention window, and updates the last-run pointer. |
| Done | Exactly one entry exists per run with a unique run id, malformed lines are ignored rather than corrupting the log, and aggregate metrics are derivable from the log alone. |
Inputs
run_id: must be supplied, non-empty, and unique within the log.started_atandended_at: must be supplied as ISO 8601 UTC timestamps (YYYY-MM-DDTHH:mm:ssZ). The entry date guard is derived fromended_at.metrics: must be supplied as a JSON object of run measurements (for example, duration, token count, model, outcome). Aggregates are computed from these fields alone.log_path: must be supplied; path to the append-only JSONL run log.last_run_pointer_path: must be supplied; path to the last-run pointer file.retention_window: optional; an ISO 8601 duration or day count. When omitted, no pruning is performed.
Procedure
- Validate inputs at the trust boundary before any mutation:
run_idis non-empty;started_atandended_atparse as ISO 8601 UTC andended_atis not beforestarted_at;metricsis a JSON object. Reject any timestamp that is not ISO-only. Scan the log for an existing line whose parsedrun_idequals the supplied one; if found, stop withrejected-duplicateand do not mutate. Done when: inputs parse and no duplicaterun_idexists. - Bound scope: open
log_pathin append-only mode. Do not read-modify-write or rewrite any prior line. Done when:log_pathis open in append-only mode. - Compose one JSONL entry as a single line:
run_id,started_at,ended_at,metrics, anddateset to the ISO date portion ofended_atas the date guard. Done when: the entry is a single line with all fields and metrics sufficient to derive aggregates. - Append the entry as exactly one line terminated by a newline, then flush. No other line is altered. Done when: exactly one line with this
run_idexists in the log. - If
retention_windowis supplied, compute the cutoff from the current UTC date minus the window. Delete whole lines whosedateprecedes the cutoff. Never alter the content of a surviving line; deletion is the only mutation permitted on prior entries. Done when: expired lines are deleted and surviving lines are unaltered. - Update the last-run pointer at
last_run_pointer_pathto an object containing the newrun_idandended_at. Done when: the pointer contains the newrun_idandended_at.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 45 lines · 63 tokens per session scan A 601eefc8a138
append-run-log is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 1,089 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-09-03.
Other skills, from other repositories
outlines
Guarantee valid JSON/XML/code structure during generation, use Pydantic models for type-safe outputs, support local models (Transformers, vLLM), and maximize inference speed with Outlines - dottxt.ai's structured generation library.
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.
setup-gitignore
Use when the user says set up gitignore, fix gitignore, or untracked files keep appearing. Writes or merges .gitignore under stable section anchors and proves reruns produce no diff. Not for remote, credential, publish, deploy, or irreversible changes.
enhance
Audit and tighten agent/plugin surfaces. Use when the user asks to enhance a plugin config, agent definition, skill, or CLAUDE.md.