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 jamestorrevillas/dev-skills --skill research-synthesisgit clone --depth 1 https://github.com/jamestorrevillas/dev-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/skills/jamestorrevillas/dev-skills/research-synthesis)<a href="https://agentmods.dev/skills/jamestorrevillas/dev-skills/research-synthesis"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/research-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/jamestorrevillas/dev-skills/research-synthesis"><img src="https://agentmods.dev/badge/skills/jamestorrevillas/dev-skills/research-synthesis.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.00060 | $0.00618 |
| Opus 5 | $0.00030 | $0.00309 |
| Sonnet 5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
research-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 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research & Synthesis
Research Process
1. DEFINE — What specific question am I trying to answer?
2. GATHER — Collect sources (docs, benchmarks, community, real usage)
3. EVALUATE — Assess source quality and recency
4. SYNTHESIZE — Extract patterns and insights across sources
5. DECIDE — Apply findings to your specific context
6. DOCUMENT — Record the decision and reasoning for future reference
Technology Evaluation Framework
For every technology comparison:
| Dimension | What to Evaluate |
|---|---|
| Fit | Does it solve your actual problem? |
| Maturity | Production-proven or experimental? |
| Community | Active maintenance, GitHub stars, Stack Overflow presence |
| Performance | Benchmarks relevant to your use case |
| Learning Curve | Team familiarity, documentation quality |
| Ecosystem | Integrations, libraries, tooling |
| Cost | License, infrastructure, ops overhead |
| Exit Cost | How hard to migrate away if needed? |
Comparison Document Template
## Decision: [technology choice]
### Context
[What problem are we solving? What are our constraints?]
### Options Considered
| | Option A | Option B | Option C |
|--|---------|---------|---------|
| Fit | | | |
| Maturity | | | |
| Performance | | | |
| Team familiarity | | | |
| Long-term risk | | | |
### Decision
[What we chose and why]
### Trade-offs Accepted
[What we give up with this choice]
### Revisit If
[Conditions that would prompt reconsideration]
Source Quality Hierarchy
- Official docs — authoritative, but may be biased toward positives
- Benchmarks — verify the benchmark matches your use case
- Production case studies — most reliable, but rare
- Community discussions — useful for gotchas and real-world issues
- Blog posts — variable quality, check date and author credentials
Always check the date. Technology moves fast — 2-year-old articles may be outdated.
Using AI for Research
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 · 91 lines · 0 tokens per session scan A c37d960603a4
research-synthesis is a skill published in the GitHub repository jamestorrevillas/dev-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 60 tokens to every session and 618 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-31.
Other skills, from other repositories
api-integration-test
Create, maintain, and run gated Go integration tests for internal APIs and service-to-service clients (HTTP/gRPC). Use for endpoint verification, contract checks with real runtime config, opt-in execution, timeout/retry safety, and integration failure triage in Go services.
create-pr
Create evidence-backed pull requests to the GitHub main branch with strict preflight, quality, and security gates. Use when users ask to create/submit/open/update a PR to main (including private repos), decide draft vs ready state, and provide reviewer-ready context for team review.
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
fuzzing-test
A Go testing guide for generating fuzz tests, which repeatedly try varied inputs to find crashes and unexpected behavior. It first checks whether the code is suitable for fuzzing.
go-benchmark
Go performance benchmarking and pprof profiling specialist. ALWAYS use when writing benchmark functions (testing.B), generating or reading pprof profiles, interpreting flame graphs, finding memory allocation hotspots, comparing implementations with benchstat, or measuring ns/op / B/op / allocs/op. In Go code contexts…