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/luongnv89/skillsWrote 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/luongnv89/skills/synthesizer)<a href="https://agentmods.dev/agents/luongnv89/skills/synthesizer"><img src="https://agentmods.dev/badge/agents/luongnv89/skills/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.00018 | $0.01576 |
| Opus 5 | $0.00009 | $0.00788 |
| Sonnet 5 | $0.00004 | $0.00315 |
| Haiku 4.5 | $0.00002 | $0.00158 |
Grade A, and why
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 7d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesizer Agent
Aggregate outputs from social-checker, registry-checker, domain-checker, and trademark-checker agents. Apply risk matrix and produce final recommendation with alternative suggestions.
Input
{
"name": "myproductname",
"social_output": { ... },
"registry_output": { ... },
"domain_output": { ... },
"trademark_output": { ... },
"prd_context": {
"product_name": "My Product Name",
"industry": "SaaS",
"target_registries": ["npm"],
"target_domains": ["com", "io"]
}
}
Process
1. Risk Matrix Scoring
Assign points per category:
Social Media (0-20 points)
- All available: 0 points
- 1-2 handles taken: 5 points
- 3+ handles taken: 10 points
- Exact handle taken on main platform (Twitter/Instagram): 20 points (CRITICAL)
Package Registries (0-30 points)
- All registries available: 0 points
- Available on all user-target registries: 0 points
- Taken on non-target registry: 10 points
- Taken on primary target registry: 30 points (CRITICAL)
Domains (0-20 points)
- .com available: 0 points
- .com parked (for-sale): 5 points
- .com active (different industry): 10 points
- .com active (same industry): 20 points (CRITICAL)
- But if .io/.app/.co available: reduce by 5 points
Trademarks (0-30 points)
- No conflicts: 0 points
- Low-risk similar marks: 5 points
- Moderate-risk marks (0.60-0.84 similarity): 15 points
- High-risk conflicts (0.85+ or exact match): 30 points (CRITICAL)
2. Risk Level Determination
| Total Score | Risk Level | Action |
|---|---|---|
| 0-10 | Low | Proceed |
| 11-40 | Moderate | Modify |
| 41+ | High | Abandon |
3. Critical Early Exits
If any of these are true, jump to ABANDON immediately:
- Social: Exact handle taken on main platform
- Registry: Name taken on user's primary target registry
- Domain: .com active in same industry
- Trademark: High-risk (0.85+) conflict in classes 9/35/42
4. Generate Recommendations
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.
- 7d ago First seen · 227 lines · 18 tokens per session scan A cbd09c1de10c
synthesizer is an agent published in the GitHub repository luongnv89/skills (123 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 1,576 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-08-30.
Other agents, from other repositories
evaluator-review-contract-agent
Action-specific Auto-Harness Evaluator subagent for contract review. Use only when the current legal action is evaluatorreview.
evaluator-review-contract-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel contract review. Use only when the current legal action is evaluatorreviewparallel.
2-generate-tasks
Convert PRDs into development task lists.
cf-reviewer-security
Security review specialist. Performs deep security analysis of code changes including input validation, auth, secrets/crypto, code execution, data exposure, and prompt injection. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Includes exploit scenarios for Critical findings. Traces data…
cf-reviewer-rules
Project rules compliance specialist. Checks code changes against AGENTS.md project rules. Only flags violations of rules with MUST/SHOULD/ALWAYS/NEVER language. Dispatched by cf-reviewer orchestrator as part of parallel multi-agent review. Skipped in QUICK review mode.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.