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 kreek/consultnpx agentmods add plugins/kreek/consult/plugingit clone --depth 1 https://github.com/kreek/consultGrade A, and why
consult 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": "consult",
"version": "13.1.0",
"description": "Consult (collaborative engineering-discipline skill pack): data, proof, security, design, and more.",
"author": {
"name": "Alastair Dawson"
},
"homepage": "https://github.com/kreek/consult",
"repository": "https://github.com/kreek/consult",
"license": "MIT",
"keywords": [
"agent-skills",
"claude-code",
"software-engineering",
"code-review",
"proof",
"security"
]
}
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 · 20 lines scan A a0263cd56862
consult is a plugin published in the GitHub repository kreek/consult (1 stars, last pushed 6d 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-08-31.
Other plugins, from other repositories
llm-redact
llm-redact proxy control: status, live traffic, sessions, redaction preview, audit verification, and guarded config editing as slash commands.
llm-redact
Plugin marketplace listing 1 plugin: llm-redact.
claude-code-tips
Developer experience essentials: GitHub Actions debugging, conversation half/quarter-cloning, context handoffs, research (Reddit and Hacker News), private GitHub search, and Claude Code version checks.
OpenOutreach
The OpenOutreach plugin for Claude Code — find B2B leads that fit, with the reason written out.
junior-flow
Helps junior developers create technical story markdown from a story tracker.
milestone-driver
Drives a GitHub milestone to completion: triages each issue for design gaps + dependency order up front, then for each buildable issue finds the root cause (or parks it), dispatches a TDD implementer subagent, runs unit + E2E tests + code review, opens a PR, and auto-merges issues on CI green. The whole loop sits…