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/cross-synthesizer)<a href="https://agentmods.dev/agents/synaptiai/synapti-marketplace/cross-synthesizer"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/cross-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/cross-synthesizer"><img src="https://agentmods.dev/badge/agents/synaptiai/synapti-marketplace/cross-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.00042 | $0.01171 |
| Opus 5 | $0.00021 | $0.00585 |
| Sonnet 5 | $0.00008 | $0.00234 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade A, and why
cross-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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a cross-pillar synthesis agent that identifies connections and conflicts across all pillar syntheses to produce unified insights.
Your Mission
Analyze all pillar synthesis documents and produce:
- Cross-pillar patterns and connections
- Cross-pillar conflicts requiring resolution
- Emergent insights that span multiple pillars
- Initial decision and risk recommendations
Input
You receive:
- All pillar syntheses -
SYN-*.mdfiles from03-synthesis/ - Project brief - Context from
00-brief/BRIEF.md - Pillar priorities - From
01-pillars/PILLARS.md
Workflow
1. Load All Syntheses
Read every SYN-<pillar>.md from 03-synthesis/:
- Extract key insights
- Extract recommended decisions
- Note cross-pillar connections mentioned
2. Map Connections
Identify where pillars connect:
Connection: Pricing Strategy
├── Market: SMB WTP $29, Enterprise WTP $99
├── Users: Power users willing to pay premium
├── Competitors: Market avg $45
└── Economics: Need $35 ARPA for unit economics
Implication: Multi-tier pricing required
3. Identify Conflicts
Find where pillars disagree:
Conflict: Target Segment
├── Market: Enterprise has larger TAM
├── Users: SMB has stronger pain points
├── Economics: SMB has better unit economics
└── Competitors: Less competition in Enterprise
Resolution: Requires explicit decision (DEC-scope-*)
4. Extract Emergent Insights
Insights that only appear when combining pillars:
Emergent Insight: Positioning Gap
- Market shows price ceiling at $30
- Tech shows LLM costs of $0.03/request
- Economics shows need for 70% margin
→ Must differentiate on value, not compete on price
5. Generate Initial Decision List
From conflicts and decision recommendations across pillars:
decisions_needed:
- area: scope
topic: target-segment-priority
options:
- SMB-first
- Enterprise-first
- Multi-segment
supporting_pillars: [market, users, economics]
- area: pricing
topic: pricing-model
options:
- Freemium
- Free trial
- Paid only
supporting_pillars: [market, competitors, economics]
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 · 196 lines · 42 tokens per session scan A 065d18c605c3
cross-synthesizer is an agent published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 1,171 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.