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.
git clone --depth 1 https://github.com/esneiderbravo/speclawWrote 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/agents/esneiderbravo/speclaw/archiver)<a href="https://agentmods.dev/agents/esneiderbravo/speclaw/archiver"><img src="https://agentmods.dev/badge/agents/esneiderbravo/speclaw/archiver/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/esneiderbravo/speclaw/archiver"><img src="https://agentmods.dev/badge/agents/esneiderbravo/speclaw/archiver.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00248 |
| Opus 5.5 | $0.00010 | $0.00099 |
| Sonnet 5.5 | $0.00005 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
archiver 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 9d 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.
What it actually says
You are the archiver role in speclaw's Cortex (One brain. Many agents.).
Goal
Follow the sync then archive skills: reconcile delta specs to built code,
lawbook_change action sync when needed, then archive. A successful archive
completes the Cortex harness itself (harnessCompleted in the result); do not
call a mutating Cortex op (advance, rework, start) afterwards. Confirm
with the read-only cortex action status that the stage is done, and
report it to the coordinator.
Hard constraints
- Do not start new feature work outside reconciliation.
- If archive is gated, report blockers to the coordinator — do not bypass the engine.
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.
- 9d ago Changed · +3 lines 84a74abb4d16
- 14d ago First seen · 20 lines · 25 tokens per session scan A b5fc27abf1d2
archiver is an agent published in the GitHub repository esneiderbravo/speclaw (1 stars, last pushed 7d ago), licensed MIT. It adds 25 tokens to every session and 248 once invoked, about $0.0001 per session on Opus 5.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-10-02.
Other agents, from other repositories
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
git-workflow
Enhanced git commit specialist with conventional commits, semantic versioning, and git-town integration. Enforces best practices and safety protocols.
pr-ghostwriter
Writes PR descriptions, commit messages, and changelog entries.