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/Jartan-LLC/grimoireWrote 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/jartan-llc/grimoire/praxis)<a href="https://agentmods.dev/plugins/jartan-llc/grimoire/praxis"><img src="https://agentmods.dev/badge/plugins/jartan-llc/grimoire/praxis/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/jartan-llc/grimoire/praxis"><img src="https://agentmods.dev/badge/plugins/jartan-llc/grimoire/praxis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
praxis 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 4d 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": "praxis",
"version": "1.7.0",
"description": "Development workflow -- issue planning, implementation, PR creation, code review with specialized reviewers, and project conventions",
"author": {
"name": "Jartan LLC",
"url": "https://github.com/Jartan-LLC"
},
"dependencies": [{ "name": "gitwise", "version": "^1.2.0" }]
}
What it installs
The manifest is a name and a version. 16 skills, 7 agents travel with it, and installing the plugin installs all of them — 603 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill frontend-patterns A 21 tokens
- Skill address-review A 14 tokens
- Skill implement-issue A 15 tokens
- Skill plan-issue A 14 tokens
- Skill create-pr A 15 tokens
- Skill logging-patterns A 16 tokens
- Skill api-error-patterns A 22 tokens
- Skill review-pr A 11 tokens
- Skill create-issue A 13 tokens
- Skill code-structure A 57 tokens
- Skill comment-hygiene A 66 tokens
- Skill readable-code A 57 tokens
- Skill review-severity A 35 tokens
- Skill code-hygiene A 38 tokens
- Skill docs-patterns A 18 tokens
- Skill testing-patterns A 23 tokens
- Agent doc-reviewer A 21 tokens
- Agent general-reviewer A 26 tokens
- Agent backend-reviewer A 22 tokens
- Agent frontend-reviewer A 24 tokens
- Agent structure-reviewer A 35 tokens
- Agent test-reviewer A 19 tokens
- Agent issue-planner A 21 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.
- 4d ago Changed 591707be9317
- 5d ago Changed 740cad04be9d
- 8d ago Changed 88bce083cb0c
- 1mo ago First seen · 11 lines scan A e16a5964e4f5
praxis is a plugin published in the GitHub repository Jartan-LLC/grimoire (2 stars, last pushed yesterday), 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
fdeops
Skills for forward deployed engineers across strategy, architecture and engineering. Use individual tasks or @fde coordination; local customer memory supports continuity.
han-linear
Linear-facing extensions to the Han suite. Adds work-items-to-linear, which creates one Linear issue per slice from a work-items file. Works through the Linear MCP server and requires it to be configured. Depends on no other Han plugin. Opt-in: installed on its own, not pulled in by the han meta-plugin.
han-reporting
Reporting and summary skills for the Han suite. Turns feature specifications into plain-language stakeholder summaries (also called executive or business summaries) with diagrams, for sharing with non-technical stakeholders before implementation kicks off.
yschimke-skills
Compose UI preview and PR-review skills for Claude Code, Codex, and Gemini.
compose-review-skills
Review Compose UI pull requests, set up preview CI, and check design parity.
han-research
Pre-planning knowledge-work skills for the Han suite: understanding a problem before anyone commits to a plan. Home of research (research an open-ended question and end at an adversarially-validated recommendation), gap-analysis (compare two artifacts and report what is missing, incomplete, or conflicting), and…