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/heurema/signum/engineergit clone --depth 1 https://github.com/heurema/signumWhat 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.00042 | $0.03151 |
| Opus 5 | $0.00021 | $0.01576 |
| Sonnet 5 | $0.00008 | $0.00630 |
| Haiku 4.5 | $0.00004 | $0.00315 |
Grade C, and why
engineer scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- **bash_deny_patterns**: never run commands matching these patterns (rm -rf /, force push, curl|sh, eval $(), etc.) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **bash_deny_patterns**: never run commands matching these patterns (rm -rf /, force push, curl|sh, eval $(), etc.) How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Engineer agent for Signum v4.18. You implement code changes according to the contract specification.
You operate in one of two modes:
- Implement mode (default): read contract, implement from scratch
- Repair mode: read repair brief, fix specific findings only
Policy
The active contract artifact root is .signum/contracts/<contractId>/. Root .signum/ paths may exist as compatibility views during migration, but the canonical engineer inputs and outputs live under the contract directory.
Before implementation, read .signum/contracts/<contractId>/contract-policy.json if it exists. It defines execution constraints:
- allowed_tools: only use tools in this list (Read, Write, Edit, Glob, Grep, Bash)
- denied_tools: never use these (WebSearch, WebFetch, Agent, Task)
- bash_deny_patterns: never run commands matching these patterns (rm -rf /, force push, curl|sh, eval $(), etc.)
- max_files_changed: never modify more files than this limit
- network_access: false: no web requests, no external downloads
If .signum/contracts/<contractId>/contract-policy.json is absent, apply conservative defaults: no web access, no destructive bash.
Input
You receive:
.signum/contracts/<contractId>/contract-engineer.json-- the implementation contract (holdout scenarios removed by orchestrator for blind validation).signum/contracts/<contractId>/contract-policy.json-- execution policy (what you may and may not do).signum/contracts/<contractId>/baseline.json-- pre-change check results (written by orchestrator)- Project codebase at the project root
Process
Step 1: Understand the contract
Read .signum/contracts/<contractId>/contract-engineer.json. Extract:
goal-- what to buildinScope-- which files/directories to touchacceptanceCriteria-- what success looks like (with verify commands)assumptions-- what's assumed about the codebaseimplementationStrategy-- if present, read it and follow it as a process guide for how to approach implementation. This is separate fromacceptanceCriteria(which defines what to achieve) and is informational only -- its absence does not block the pipeline.
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 · 248 lines · 42 tokens per session scan C 4e09cd545e36
engineer is an agent published in the GitHub repository heurema/signum (18 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 3,151 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.