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/product-on-purpose/agent-skills-toolkitWrote 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/product-on-purpose/agent-skills-toolkit/probe-collision-a)<a href="https://agentmods.dev/plugins/product-on-purpose/agent-skills-toolkit/probe-collision-a"><img src="https://agentmods.dev/badge/plugins/product-on-purpose/agent-skills-toolkit/probe-collision-a.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
probe-collision-a 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.
What it actually says
{
"name": "probe-collision-a",
"version": "0.0.0",
"description": "PROBE FIXTURE, not a real plugin. One of two plugins shipping an identically named skill, to establish whether component names share a pool across plugins. This is side A.",
"license": "Apache-2.0",
"author": {
"name": "product-on-purpose"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 41 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 10 lines scan A c8c3a5fccd64
probe-collision-a is a plugin published in the GitHub repository product-on-purpose/agent-skills-toolkit (2 stars, last pushed today), licensed Apache-2.0. 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-08-31.
Other plugins, from other repositories
paperthin
Low-level agentic design patterns. Turning old engineering wisdom into reflexes your agent reaches for on its own—on any agent.
jaiskills
Orchestration (insistir, constatar, remoto), prompting (metaprompt), knowledge compounding, file-based TODOs, an illustrated Claude Agent SDK wizard, and OpenAI tooling (askcodex, image-to-frontend) as one Claude Code plugin.
context-firewall
Context Firewall: use sub-agents to preprocess large inputs with evidence contracts and low-cost verification.
devloop
Iterate until ready to merge: create branch, fix, commit, open PR, wait for AI review, apply feedback, repeat.
sync-claude-skills-to-codex
Sync Claude Code skills to Codex CLI via symlinks. Share your skill library between both AI coding assistants.
meta-harness
Intelligent harness creator for Claude Code. Analyzes any project, selects optimal patterns from a curated library of proven architectures (ECC, gstack, OmO, OMC), and generates tailored agents, skills, hooks, and rules — while auto-checking official features to avoid duplication.