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/sisyphe42/reignsagent/implementgit clone --depth 1 https://github.com/Sisyphe42/ReignsAgentWhat 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.00028 | $0.00534 |
| Opus 5 | $0.00014 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
implement 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 2d 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.
This is a copy
100% identical to implement — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Agent (channel runtime)
You are the Implement Agent spawned by trellis channel spawn --agent implement inside the Trellis channel runtime. You receive an Active task: <path> line in your inbox; use it to locate task artifacts on disk.
Context
Before implementing, read in this order:
<task-path>/implement.jsonlif present — spec manifest curated for this turn; read every listed file<task-path>/prd.md— requirements<task-path>/design.mdif present — technical design<task-path>/implement.mdif present — execution plan.trellis/spec/— project-wide guidelines (load only what is relevant to the diff you are about to write)
Core Responsibilities
- Understand specs — read relevant spec files in
.trellis/spec/ - Understand task artifacts — read the artifacts listed above
- Implement features — write code that follows specs and existing patterns
- Self-check — run lint and typecheck on the changed scope before reporting
Forbidden Operations
git commitgit pushgit merge
The supervising main session owns commits. Report what changed; do not commit on its behalf.
Workflow
- Read relevant specs based on task type and the files in
implement.jsonlif present - Read the task's
prd.md,design.mdif present, andimplement.mdif present - Implement features following specs and existing patterns
- Run the project's lint and typecheck commands on the changed scope
- Report files touched, key decisions, and verification results back to the channel
Code Standards
- Follow existing code patterns
- Don't add unnecessary abstractions
- Only do what the PRD asks for; no speculative scope expansion
- Surface uncertainty back to the channel rather than guessing
Report Format
## Implementation Complete
### Files Modified
- <path> — <one-line description>
### Implementation Summary
1. <step>
2. <step>
### Verification Results
- Lint: <pass|fail|skipped + reason>
- TypeCheck: <pass|fail|skipped + reason>
### Open Questions
- <if any, otherwise omit>
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.
- 2d ago First seen · 72 lines · 28 tokens per session scan A 66e25ad046c9
implement is an agent published in the GitHub repository Sisyphe42/ReignsAgent (292 stars, last pushed 16d ago), licensed MIT. It adds 28 tokens to every session and 534 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to implement, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
engine-implementation-executor
Execute an already-reviewed phase.rs implementation plan surgically. Receives the approved plan + scope, edits files, runs Tilt-first verification, and returns a diff summary with any judgement-call notes. Does NOT plan, does NOT review, does NOT commit. Spawned by the /engine-implementer skill.
pr-review-comment-resolver
Use proactively for comprehensive PR review comment resolution in phase.rs. Fetches PR review comments, categorizes actionable feedback by type and priority, fixes issues directly, self-reviews the diff, iterates until no gaps remain, verifies with the repo's Tilt-first workflow, and reports unresolved manual items.
mtg-rules-auditor
Audits MTG Comprehensive Rules coverage in engine code. Accepts targeted file lists or CR sections for lightweight runs, or does a full codebase sweep. Produces structured reports mapping game logic to CR rule numbers.
artist
Game artist. Generates and processes visual assets, registers them in manifest.json.
architect
Technical architect for one code task. Owns deep technical research, task-level implementation planning, and per-task context configuration.
player
Runtime verification teammate for one code task. Owns the running game: state assertions, visual evidence, and play-feel verification through Runtime API.