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 bostonaholic/rpikit --skill synthesizing-researchgit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/bostonaholic/rpikit/synthesizing-research)<a href="https://agentmods.dev/skills/bostonaholic/rpikit/synthesizing-research"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/synthesizing-research/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/bostonaholic/rpikit/synthesizing-research"><img src="https://agentmods.dev/badge/skills/bostonaholic/rpikit/synthesizing-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.00710 |
| Opus 5 | $0.00018 | $0.00355 |
| Sonnet 5 | $0.00007 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
Grade A, and why
synthesizing-research 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 11d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research Synthesis
Consolidate research for: $ARGUMENTS
Purpose
When research is conducted in parallel — multiple agents exploring different aspects of a problem — each produces a separate findings file. This skill combines those files into one self-contained document that a reader with no prior context can understand completely.
Process
1. Locate Research Files
Search for research files related to the topic:
Glob pattern: docs/plans/*-<topic>-*.md
Exclude: *-plan.md, *-research.md (the consolidated output)
If no files are found, ask the user to specify the file paths.
2. Read All Source Files
Read each research file completely. Note:
- Key findings from each source
- Overlapping or contradictory information
- Gaps — topics mentioned but not investigated
- Confidence levels stated by each researcher
3. Organize by Theme
Restructure findings by theme, NOT by source. Multiple researchers may have found related information — group it together rather than presenting each researcher's output sequentially.
Themes to look for:
- Architecture and design patterns
- Data flow and state management
- External dependencies and APIs
- Security and performance considerations
- Testing patterns and coverage
- Gaps and open questions
4. Write Consolidated Document
Create the synthesis at: docs/plans/YYYY-MM-DD-<topic>-research.md
(Use today's date in YYYY-MM-DD format)
# Research: <Topic> (YYYY-MM-DD)
## Problem Statement
[What is being investigated and why]
## Requirements
[Key requirements gathered from research]
## Findings
### [Theme 1]
[Findings organized by theme, not by source document]
### [Theme 2]
[Continue for each theme...]
## External Research
[Findings from web research with source citations and confidence
assessments]
## Technical Constraints
[Limitations, dependencies, and compatibility concerns]
## Open Questions
[Questions that remain unanswered across all research]
## Recommendations
[Synthesis of all findings into actionable recommendations]
## Sources
| Document | Researcher | Focus Area |
| -------- | ---------- | ---------- |
| [path] | [agent] | [scope] |
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.
- 11d ago First seen · 131 lines · 37 tokens per session scan A 7cd23fb0adbe
synthesizing-research is a skill published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed 4d ago), licensed MIT. It adds 37 tokens to every session and 710 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-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
api-docs
Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself. Use when the user asks for API reference, to document a module, or to write usage docs for a public interface.
research
Run deep research on any topic using the Deep Research MCP server. Use this skill whenever the user wants to research a topic, gather information, find sources, or create a research document. Triggers on: 'research this', 'find out about', 'gather information on', 'I need to understand', 'deep dive into', or any…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
Workspace Data Analyst
Analyze CSV files in the workspace and summarize insights.
run_jinx
Execute a jinx by name (already loaded on the team) or by filesystem path (e.g. a freshly createdjinx that isn't yet registered), passing input values as a JSON object. Returns the jinx's output field or the full context dict. Use this to run a jinx you just wrote without exiting the session.