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/peteski22/agent-pragmaWrote 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/peteski22/agent-pragma/pragma)<a href="https://agentmods.dev/plugins/peteski22/agent-pragma/pragma"><img src="https://agentmods.dev/badge/plugins/peteski22/agent-pragma/pragma/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/plugins/peteski22/agent-pragma/pragma"><img src="https://agentmods.dev/badge/plugins/peteski22/agent-pragma/pragma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
pragma 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 1mo 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
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "pragma",
"displayName": "Pragma",
"version": "4.4.4",
"description": "Deterministic linting hooks, semantic code validators, and a multi-LLM advisory council. Enforces coding rules mechanically — not by suggestion.",
"author": {
"name": "Peter Wilson"
},
"repository": "https://github.com/peteski22/agent-pragma",
"license": "Apache-2.0",
"keywords": ["validation", "code-quality", "go", "python", "typescript", "security", "linting", "llm-council"]
}
What it installs
The manifest is a name and a version. 12 skills, 2 agents travel with it, and installing the plugin installs all of them — 237 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill implement A 10 tokens
- Skill python-style A 11 tokens
- Skill error-handling A 10 tokens
- Skill go-effective A 13 tokens
- Skill go-proverbs A 11 tokens
- Skill state-machine A 9 tokens
- Skill typescript-style A 14 tokens
- Skill review A 12 tokens
- Skill security A 8 tokens
- Skill validate A 9 tokens
- Skill star-chamber A 22 tokens
- Skill setup-project D 21 tokens
- Agent security A 51 tokens
- Agent star-chamber A 36 tokens
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.
- 1mo ago Changed 2ddfe8f42959
- 1mo ago Changed 9cfd2b0a476f
- 1mo ago First seen · 14 lines scan A e2b0429f44d7
pragma is a plugin published in the GitHub repository peteski22/agent-pragma (24 stars, last pushed 1mo ago), 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-30.
Other plugins, from other repositories
frontier
Standards written and audited by Claude Fable 5: make Opus, Sonnet, GPT, or Gemini produce work close to its bar. 21 craft rubrics, best-of-N candidates, convergence sweeps, a taste gate with permanent distillation.
architecture-governance
Establish architecture governance, design fitness functions, manage tech debt, and ensure compliance. Build sustainable architecture practices.
quality-attributes
Design for non-functional requirements: scalability, reliability, performance, security, maintainability. Master quality attribute analysis and architectural fitness functions.
code-review-assistant
Automated code review with severity levels and actionable feedback.
community-coding
Code quality, review, and deployment skills vendored from the web.
architect-toolkit
Essential architect tools: katas, interview prep, review facilitation, mentoring, anti-patterns, audits, and pattern catalogs.