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 dork-labs/dorkosnpx agentmods add plugins/dork-labs/dorkos/valid-plugingit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/valid-plugin)<a href="https://agentmods.dev/plugins/dork-labs/dorkos/valid-plugin"><img src="https://agentmods.dev/badge/plugins/dork-labs/dorkos/valid-plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
valid-plugin 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 yesterday.
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": "valid-plugin",
"version": "1.0.0",
"description": "A valid plugin fixture for the install-flow tests"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 13 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.
- yesterday First seen · 6 lines scan A 64769643ba71
valid-plugin is a plugin published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), 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
claude-therapy
Structured human-Claude collaboration retrospectives, session analysis, and interaction repair tools.
context-grounding
--.
pyright-lsp
Python language server (Pyright) for type checking and code intelligence.
plugin-dev
Plugin development toolkit with skills for creating agents, commands, hooks, MCP integrations, and comprehensive plugin structure guidance.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.
claude-plugins-official marketplace
Directory of popular Claude Code extensions including development tools, productivity plugins, and MCP integrations.