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.
/plugin marketplace add duthaho/skillhubnpx agentmods add plugins/duthaho/skillhub/researchgit clone --depth 1 https://github.com/duthaho/skillhubWrote 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/plugins/duthaho/skillhub/research)<a href="https://agentmods.dev/plugins/duthaho/skillhub/research"><img src="https://agentmods.dev/badge/plugins/duthaho/skillhub/research.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
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 2d 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.
What it actually says
{
"name": "research",
"description": "Cited, engagement-ranked research: community pulse, tech-decision verdicts, job-fit scoring, citation auditing, and competitive recon",
"version": "1.0.0",
"source": "./",
"strict": false,
"skills": [
"./.claude/skills/pulse",
"./.claude/skills/verdict",
"./.claude/skills/jobfit",
"./.claude/skills/factcheck",
"./.claude/skills/scout",
"./.claude/skills/priorart",
"./.claude/skills/ideate"
]
}What it installs
The manifest is a name and a version. 7 skills travel with it, and installing the plugin installs all of them — 1,331 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside marketplace.json#research in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 16 lines scan A d5e44b86aa29
research is a plugin published in the GitHub repository duthaho/skillhub (9 stars, last pushed 12d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
ecto
Compatibility namespace for the Elixir/Phoenix plugin's /ecto: commands.
longbridge
Longbridge securities skill family (v2): 13 consolidated skills replacing the previous 127-skill set. Full coverage of market data, fundamentals, research, portfolio & account, quantitative strategies, and more. Requires reinstall (not just update) when upgrading from v1.x — see scripts/reinstall.sh.
sound
Code taste as installable rules. Probe a repo's stack, select only the rules its code shows a surface for (evidence-cited per rule), confirm, and scaffold a browsable .claude/sound/ rule map (surfaced by the sound:prime skill). Installed rules are user-owned; re-runs reconcile.
spring-clean
Two passes over a repo. spring-clean measures against a declared scoreboard, deletes or gitignores what does not belong, relocates dev docs, notes, clones and dumps to a -workspace repo, splits oversized files, draws package boundaries and writes its plan to a numbered unit list that survives a dead context. w.
portal-skills
Platform engineering and security skills: GitLab CI/CD + Helm chart generation for Kubernetes, data-driven pod rightsizing from Prometheus, a proactive secure-coding baseline, and a deep OWASP reference (Top 10:2025, LLM Top 10, Agentic AI).
neatcontext marketplace
Save Claude Code work as reusable, domain-aware context.