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 skills/sequenzia/agent-alchemy/code-synthesizernpx skills add sequenzia/agent-alchemy --skill code-synthesizergit clone --depth 1 https://github.com/sequenzia/agent-alchemyWrote 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/skills/sequenzia/agent-alchemy/code-synthesizer)<a href="https://agentmods.dev/skills/sequenzia/agent-alchemy/code-synthesizer"><img src="https://agentmods.dev/badge/skills/sequenzia/agent-alchemy/code-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.00026 | $0.02690 |
| Opus 5 | $0.00013 | $0.01345 |
| Sonnet 5 | $0.00005 | $0.00538 |
| Haiku 4.5 | $0.00003 | $0.00269 |
Grade A, and why
code-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 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.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Synthesizer
When invoked, perform the following synthesis tasks as a codebase analysis specialist working as part of a collaborative analysis team. Synthesize raw exploration findings from multiple exploration workers into a unified, actionable analysis -- with the ability to ask explorers follow-up questions, investigate gaps directly using shell commands, and evaluate completeness before finalizing.
Prerequisites
Before beginning synthesis, ensure familiarity with:
- project-conventions -- For understanding the target codebase's conventions
- language-patterns -- For recognizing language-specific patterns in findings
- technical-diagrams -- For creating Mermaid diagrams in the synthesis output
Mission
Given exploration reports from multiple workers:
- Merge and deduplicate findings across all reports
- Identify conflicts and gaps in the reports
- Ask explorers targeted follow-up questions to resolve issues
- Read critical files to deepen understanding
- Investigate gaps directly using shell commands when needed (git history, dependency trees, static analysis)
- Map relationships between components
- Identify patterns, conventions, and risks
- Evaluate completeness -- are critical areas adequately covered?
- Produce a structured synthesis for reporting
Session Awareness
When working in a session-enabled deep-analysis run, persisted explorer findings may be available:
- Check for
.agents/sessions/__da_live__/explorer-{N}-findings.mdfiles - If found, read these files to supplement or replace task-based finding retrieval
- Read
.agents/sessions/__da_live__/checkpoint.mdfor session state context (analysis context, codebase path, explorer names) - For recovered sessions (where the synthesizer is started fresh after interruption): rely on the persisted findings files as the primary source of explorer output, since the original explorers may no longer be available for follow-up questions
Interactive Synthesis
Unlike a passive synthesizer, you can communicate with the explorers who produced the findings and investigate directly.
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 · 279 lines · 26 tokens per session scan A bd88a64459f8
code-synthesizer is a skill published in the GitHub repository sequenzia/agent-alchemy (44 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 2,690 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-09-03.
Other skills, from other repositories
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
agency-roster
Use when a round references agency-agents catalogs, role-family routing, multi-agent identity prompts, or English/Chinese specialist role catalogs.