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 skills add prime-radiant-inc/greenfield --skill multi-source-synthesisgit clone --depth 1 https://github.com/prime-radiant-inc/greenfieldWrote 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/prime-radiant-inc/greenfield/multi-source-synthesis)<a href="https://agentmods.dev/skills/prime-radiant-inc/greenfield/multi-source-synthesis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/multi-source-synthesis/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/skills/prime-radiant-inc/greenfield/multi-source-synthesis"><img src="https://agentmods.dev/badge/skills/prime-radiant-inc/greenfield/multi-source-synthesis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 16 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
- high Prompt Injection · line 422 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00053 | $0.08093 |
| Opus 5 | $0.00026 | $0.04047 |
| Sonnet 5 | $0.00011 | $0.01619 |
| Haiku 4.5 | $0.00005 | $0.00809 |
Grade A, and why
multi-source-synthesis 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 10d 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 — 850 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Source Synthesis
You transform raw Layer 1 intelligence into structured synthesis documents. You merge findings from multiple independent analysis modes into corroborated, conflict-resolved behavioral descriptions that Layer 3 can write deep specs from.
The Core Principle
Merge independently. Resolve conflicts explicitly. Cite everything. Miss nothing.
- Merge: Every behavioral claim from every available mode gets collected, compared, and synthesized.
- Resolve: When modes disagree, apply the conflict resolution hierarchy. Record BOTH claims with provenance.
- Cite: Every synthesized claim traces back to Layer 1 evidence with
<!-- cite: -->annotations. - Complete: Every feature, every component, every interface, every module must appear in synthesis output.
Layer 2 Pipeline
digraph layer2_pipeline {
rankdir=TB;
subgraph cluster_inputs {
label="Layer 1 Intelligence Sources";
style=dashed;
"Source Code Analysis" [shape=folder];
"Public Documentation" [shape=folder];
"SDK / Ecosystem" [shape=folder];
"Runtime Observation" [shape=folder];
"Binary Analysis" [shape=folder];
"Community Intelligence" [shape=folder];
}
subgraph cluster_phase1 {
label="Phase 1 (parallel)";
style=filled;
fillcolor="#e8f4e8";
"feature-discoverer" [shape=box];
"architecture-analyst" [shape=box];
"api-extractor" [shape=box];
}
subgraph cluster_phase2 {
label="Phase 2";
style=filled;
fillcolor="#e8e8f4";
"analysis-synthesizer" [shape=box];
}
subgraph cluster_phase3 {
label="Phase 3";
style=filled;
fillcolor="#f4e8e8";
"module-mapper" [shape=box];
}
"Source Code Analysis" -> "feature-discoverer";
"Source Code Analysis" -> "architecture-analyst";
"Source Code Analysis" -> "api-extractor";
"Public Documentation" -> "feature-discoverer";
"Public Documentation" -> "architecture-analyst";
"Public Documentation" -> "api-extractor";
"SDK / Ecosystem" -> "feature-discoverer";
"SDK / Ecosystem" -> "api-extractor";
"Runtime Observation" -> "feature-discoverer";
"Runtime Observation" -> "architecture-analyst";
"Runtime Observation" -> "api-extractor";
"Binary Analysis" -> "architecture-analyst";
"Community Intelligence" -> "feature-discoverer";
"feature-discoverer" -> "analysis-synthesizer";
"architecture-analyst" -> "analysis-synthesizer";
"api-extractor" -> "analysis-synthesizer";
"Source Code Analysis" -> "analysis-synthesizer" [style=dashed, label="raw L1"];
"Public Documentation" -> "analysis-synthesizer" [style=dashed, label="raw L1"];
"Runtime Observation" -> "analysis-synthesizer" [style=dashed, label="raw L1"];
"analysis-synthesizer" -> "module-mapper";
"feature-discoverer" -> "module-mapper";
"architecture-analyst" -> "module-mapper";
"api-extractor" -> "module-mapper";
"module-mapper" -> "Layer 3 Deep Dives" [shape=doublecircle];
}
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.
- 10d ago First seen · 850 lines · 53 tokens per session scan A ae7d65733801
multi-source-synthesis is a skill published in the GitHub repository prime-radiant-inc/greenfield (273 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 8,093 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 skills, from other repositories
benchmark
Local-only regression / benchmark skill for ui-clone-skills maintainers. Drives the standard ui-reverse-engineering pipeline against the canonical reference site (https://realfood.gov) and records AE/SSIM, iteration count, gate fail counts, and outcome to benchmark/history.csv so prompt / sub-doc / model-version drift…
ui-capture
Capture baseline evidence from a live website URL: screenshots, scroll states, hover/click behavior, parallax, timers, and transition recordings. Use when reference artifacts are needed before implementation or comparison; not to build or diagnose a clone.
write-test-plans
Interactive workflow for writing new Speky test plans for requirements lacking coverage, guided by the Speky MCP server.
speky-workflow
Guidelines for working with Speky requirements and tests via the speky MCP server tools.
SPI Flash Dump via OpenOCD
This skill should be used when the user asks to "dump SPI flash", "read EEPROM through OpenOCD", "dump flash via MCU", "read SPI through debug interface", "extract firmware from SPI", or mentions scenarios involving SPI flash connected to a microcontroller with SWD/JTAG debug access. Provides comprehensive guidance…
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…