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/geekatron/jerryWrote 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/geekatron/jerry/tspec-generator)<a href="https://agentmods.dev/agents/geekatron/jerry/tspec-generator"><img src="https://agentmods.dev/badge/agents/geekatron/jerry/tspec-generator/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/geekatron/jerry/tspec-generator"><img src="https://agentmods.dev/badge/agents/geekatron/jerry/tspec-generator.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.00101 | $0.03670 |
| Opus 5.5 | $0.00040 | $0.01468 |
| Sonnet 5.5 | $0.00020 | $0.00734 |
| Haiku 4.5 | $0.00010 | $0.00367 |
Grade A, and why
tspec-generator 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 1mo 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 1mo ago First seen · 263 lines · 101 tokens per session scan A ad97384084bb
tspec-generator is an agent published in the GitHub repository geekatron/jerry (37 stars, last pushed 5d ago), with no licence file. It adds 101 tokens to every session and 3,670 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
orc-implementer
Executor role — senior-developer agent that implements a defined slice list from a plan + failing test(s). Receives 1 or N slice IDs from the caller; drives each through the TDD red-green-refactor cycle, commits per slice via orc:git-commit, runs the full suite between slices. Default executor in /orc:flow Phase 5…
python-test-engineer
Write behavior-driven suites and drive TDD workflows in Python. TRIGGER WHEN: writing tests, improving test coverage, fixing broken tests, setting up pytest configurations, or practicing red-green-refactor workflows. DO NOT TRIGGER WHEN: building new features from scratch or designing system architecture (use…
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
cook
Feature implementation orchestrator — handles 70% of requests. Full TDD cycle: understand → plan → test → implement → verify → commit. Use for ANY code modification (features, bugs, refactors, security).
safe-refactorer
Specializes in restructuring code without changing observable behavior. Uses test-driven development principles to guarantee regressions are avoided. Use when migrating frameworks or cleaning up legacy components.