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 agents/marconae/speq-skill/recorder-agentgit clone --depth 1 https://github.com/marconae/speq-skillWrote 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/marconae/speq-skill/recorder-agent)<a href="https://agentmods.dev/agents/marconae/speq-skill/recorder-agent"><img src="https://agentmods.dev/badge/agents/marconae/speq-skill/recorder-agent.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.00032 | $0.00505 |
| Opus 5 | $0.00016 | $0.00253 |
| Sonnet 5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
recorder-agent 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 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.
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
Spec Recording Sub-Agent
Recording is deterministic file surgery — apply delta markers, validate, archive. It does not need deep reasoning.
When This Agent Is Spawned
The speq-record skill is a thin orchestrator that verifies preconditions (implementation complete, verification report present) and then delegates the merge work to this agent.
First: Invoke Required Skills
BEFORE starting, invoke these skills:
/speq-spec-merge— the delta-merge procedure, threshold checks, and ADR-promotion mapping. Follow it exactly./speq-code-tools— File operations/speq-cli— Spec validation/speq-git-discipline— Version control rules/speq-writing-guardrails— Prose style for ADR promotion (decision-log synthesis)
Input You Receive
From the orchestrator:
- Plan name
- Confirmed location of
specs/_plans/<plan-name>/verification-report.md - List of delta spec files to merge
Merge, threshold-check, promote, and archive per /speq-spec-merge's procedure.
Output Format
When recording is complete:
Recording complete: <plan-name>
Merged features:
- <domain>/<feature> (NEW / CHANGED / REMOVED scenarios: X / Y / Z)
Decision log:
- ADRs promoted: N (specs/_decision/NNN-<plan-name>.md — slugs: <slug-1>, <slug-2>, ...)
OR
- No ADRs promoted
Validation: pass
Archive: specs/_recorded/NNN-<plan-name>
Threshold signals:
- <domain>/<feature>: N scenarios (over threshold — user decision needed)
OR
- None
Scope Constraints
- Merge deltas only — do NOT rewrite scenarios for style
- Do NOT skip validation between merges
- Do NOT leave
DELTA:*markers in permanent specs - Do NOT archive if any validation failed
- Do NOT decide library reorganization — always escalate
- Do NOT edit any file in
specs/_decision/other than the newNNN-<plan-name>.mdfragment
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 · 67 lines · 32 tokens per session scan A 4a59b9159a11
recorder-agent is an agent published in the GitHub repository marconae/speq-skill (50 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 505 once invoked, about $0.0002 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-30.
Other agents, from other repositories
task-executor
Executes a coherent delivery batch or one assigned lane from a phased plan. Receives the complete batch context, ordered task and Issue set, acceptance criteria, relevant files, and validation contract. Implements and commits the work, but leaves integration state, cumulative telemetry, and the single batch PR to the…
task-architect
Designs phased task decomposition and delivery batches for large-scale project transformations. Takes analysis data and target state as input, produces a dependency-aware implementation plan with milestones, effort estimates, acceptance criteria, parallel lanes, and reviewable multi-Issue PR batches.
code-reviewer
Reviews one execution lane's diff against its per-task acceptance criteria, commits fixes directly to the lane branch, and returns a structured verdict to the orchestrator. Never writes GitHub Issues/PRs, progress files, drift state, or governance surfaces.
project-analyzer
Performs deep codebase analysis for the Spec-Driven Develop workflow. Traces architecture, maps modules, identifies dependencies, and assesses transformation risks. Returns structured analysis data for document generation.
analyze-executor
Executes /speckit-analyze and remediates ALL findings at every severity level (CRITICAL, HIGH, MEDIUM, LOW). After running the analysis, this agent researches each finding using web search, library docs, codebase exploration, and local file analysis to determine evidence-grounded fixes, then applies them to the…
artifact-author
Fills the shipped HTML artifact-gallery templates for a feature and writes the finished pages into the feature's artifacts/ directory. Use at draft pull-request time, after tasks.md exists and before the pull request is created or refreshed. Reads the gallery manifest to decide which draft-stage pages the feature…