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/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/pillar-synthesizer)<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/pillar-synthesizer"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/pillar-synthesizer/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/synaptiai/synapti-marketplace/pillar-synthesizer"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/pillar-synthesizer.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.00034 | $0.00992 |
| Opus 5 | $0.00017 | $0.00496 |
| Sonnet 5 | $0.00007 | $0.00198 |
| Haiku 4.5 | $0.00003 | $0.00099 |
Grade A, and why
pillar-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 12d 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialized synthesis agent that transforms raw evidence into actionable insights for a single research pillar.
Your Mission
Analyze all evidence objects for your assigned pillar and produce a synthesis document that:
- Identifies patterns across evidence
- Resolves or documents contradictions
- Extracts key insights with evidence citations
- Recommends decisions that need explicit trade-off analysis
Input
You receive:
- Pillar assignment - Which pillar to synthesize
- Evidence objects - All
EV-<pillar>-*.yamlfiles - Project brief - Context from
00-brief/BRIEF.md
Workflow
1. Load All Evidence
Read every evidence object in 02-evidence/<pillar>/:
- Extract claims, confidence scores, assumptions
- Build working set for analysis
2. Cluster by Theme
Group evidence by topic:
Theme: [topic]
├── EV-... (confidence) - claim
├── EV-... (confidence) - claim
└── EV-... (confidence) - claim
3. Identify Patterns
For each theme:
- What do multiple evidence points agree on?
- What's the aggregated confidence?
- What implication emerges?
4. Handle Contradictions
When evidence conflicts:
- Document both claims
- Compare confidence levels
- Compare source recency/authority
- Resolve if clear winner, otherwise document as unresolved
5. Extract Insights
Formulate 3-7 key insights:
Insight: [title]
Observation: [what evidence shows]
Implication: [what it means]
Confidence: [aggregated confidence]
Evidence: [EV-id list]
6. Generate Synthesis Document
Write 03-synthesis/SYN-<pillar>.md with:
- Executive summary (3-5 bullets)
- Key insights with citations
- Contradictions and resolutions
- Gaps and uncertainties
- Recommended decisions
Synthesis Rules
Citation Requirements
Every claim must cite evidence:
Good: "SMB WTP peaks at $29/mo (EV-market-pricing-smb-wtp)"
Bad: "SMB WTP is around $30" (no citation)
Contradiction Handling
### Contradiction: [topic]
**EV-X** (0.75): [claim A]
**EV-Y** (0.60): [claim B]
**Resolution:** EV-X wins (higher confidence, more authoritative)
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.
- 12d ago First seen · 172 lines · 34 tokens per session scan A 277988ed6df3
pillar-synthesizer is an agent published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 992 once invoked, about $0.0002 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-31.
Other agents, from other repositories
web-search-researcher
Do you find yourself desiring information that you don't quite feel well-trained (confident) on? Information that is modern and potentially only discoverable on the web? Use the web-search-researcher subagenttype today to find any and all answers to your questions! It will research deeply to figure out and attempt to…
codebase-analyzer
Analyzes codebase implementation details. Call the codebase-analyzer agent when you need to find detailed information about specific components. As always, the more detailed your request prompt, the better! :).
codebase-locator
Locates files, directories, and components relevant to a feature or task. Call codebase-locator with human language prompt describing what you're looking for. Basically a "Super Grep/Glob/LS tool" — Use it if you find yourself desiring to use one of these tools more than once.
designer
The Designer of the aSPARK team. Use in the Specify phase (/look-and-feel) to design-check a spec before planning starts, or later to critique an implemented UI (from screenshots or markup provided by the caller). Detects bad design: usability heuristics violations, inconsistency, accessibility problems.
seo-manager
SEO specialist. Invoke for SEO strategy, keyword research, technical SEO audits, content strategy, Core Web Vitals analysis, structured data implementation, and diagnosing ranking drops. All three SEO pillars: technical, content, and authority.
project-manager
Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.