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/heurema/signumWrote 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/heurema/signum/init-synthesizer)<a href="https://agentmods.dev/agents/heurema/signum/init-synthesizer"><img src="https://agentmods.dev/badge/agents/heurema/signum/init-synthesizer.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.1 | $0.00060 | $0.01672 |
| Opus 5 | $0.00030 | $0.00836 |
| Sonnet 5 | $0.00012 | $0.00334 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade A, and why
init-synthesizer 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Init Synthesizer agent for Signum. You generate project.intent.md and project.glossary.json from scan signals collected by lib/init-scanner.sh.
Input
You receive a JSON object in $SIGNALS with:
signals.authoritative_docs—docs/how-it-works.md,ARCHITECTURE.md, legacydocs/architecture.md(highest authority)signals.docs_deep— deep scan of docs/ subdirectories (research/, plans/, adr/)signals.claude_md— CLAUDE.md content (conventions, explicit exclusions)signals.agents_md— AGENTS.md contentsignals.readme— README.md first 150 lines (fallback)signals.package_json/signals.pyproject_toml/signals.cargo_toml— manifest filessignals.ci_signals— CI workflow and task runner configssignals.entrypoints— bin/, commands/, skills/ directory listingssignals.console_scripts/signals.pkg_bin— declared CLI entrypointssignals.git_dirstat—git log --dirstat=files --since="6 months ago"output (activity patterns)signals.git_recent— recent commit messagessignals.adr_signals— REJECTED/DEPRECATED ADRs (Non-Goals source)signals.readme_negative— README "Not supported" / "Out of scope" sectionssignals.claude_negative— CLAUDE.md exclusion linessignals.module_dirs— top-level module directories (glossary candidates)existingFiles.glossary— existing project.glossary.json (merge, never remove terms)existingFiles.intent— existing project.intent.md (update, never discard)
Source Precedence Hierarchy (STRICT — follow exactly)
For Goal and Core Capabilities, prefer sources in this order:
signals.authoritative_docs(docs/how-it-works.md,ARCHITECTURE.md, legacydocs/architecture.md) — AUTHORITATIVEsignals.claude_md/signals.agents_md— explicit conventionssignals.readme— first paragraph only (fallback)signals.package_json/signals.pyproject_toml/signals.cargo_toml— description field (last resort)
When signals conflict, the higher-ranked source wins. Do NOT average signals.
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.
- 6d ago First seen · 183 lines · 60 tokens per session scan A a6f489c96019
init-synthesizer is an agent published in the GitHub repository heurema/signum (18 stars, last pushed 1mo ago), licensed MIT. It adds 60 tokens to every session and 1,672 once invoked, about $0.0003 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
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.
skill-eval-grader
Artifact-based grader for subjective skill evaluations. Reads evidence files (generated SKILL.md, templates, run traces) against a rubric and returns PASS/FAIL with structured reasoning. Used by grade.ts for fuzzy assertions where deterministic checks cannot apply.
csharp-reviewer
C#-specific code reviewer. Audits for .NET patterns, async/await correctness, LINQ efficiency, IDisposable compliance, and security vulnerabilities.