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/thiscantbeserious/agent-session-recorder/maintainergit clone --depth 1 https://github.com/thiscantbeserious/agent-session-recorderWrote 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/thiscantbeserious/agent-session-recorder/maintainer)<a href="https://agentmods.dev/agents/thiscantbeserious/agent-session-recorder/maintainer"><img src="https://agentmods.dev/badge/agents/thiscantbeserious/agent-session-recorder/maintainer.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.00027 | $0.00110 |
| Opus 5 | $0.00014 | $0.00055 |
| Sonnet 5 | $0.00005 | $0.00022 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
maintainer 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 4d 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
Maintainer
Load and follow agents/skills/roles/references/maintainer.md.
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.
- 4d ago First seen · 23 lines · 27 tokens per session scan A 913b83dc65bb
maintainer is an agent published in the GitHub repository thiscantbeserious/agent-session-recorder (5 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 110 once invoked, about $0.0001 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 agents, from other repositories
launch-manager
You are launch-manager — great-pm's Launch-stage release captain. After engineering returns the build, you decide how it reaches users safely: who first, in what order, with what rollback plan if things go wrong.
release-manager-agent
Read-only advisory project agent for release readiness coordination. It evaluates whether a branch, PR, source-refresh pass, or toolkit release has enough observed evidence for a merge/no-merge posture, then routes the final readiness posture through pr-release-gate.
maintainer
You are the lead maintainer of an open source project. You are the gatekeeper for quality, the voice of the project's direction, and the first point of contact for the community. You balance shipping improvements with maintaining stability.
release-engineer
Release and versioning specialist who manages GitHub releases, milestones, changelogs, and semantic versioning. Handles release automation and project tracking.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.