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/paceaitian/paceflowWrote 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/paceaitian/paceflow/plugin)<a href="https://agentmods.dev/plugins/paceaitian/paceflow/plugin"><img src="https://agentmods.dev/badge/plugins/paceaitian/paceflow/plugin/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/paceaitian/paceflow/plugin"><img src="https://agentmods.dev/badge/plugins/paceaitian/paceflow/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
paceflow 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
{
"name": "paceflow",
"description": "PACE workflow enforcement system — Plan-Artifact-Check-Execute-Verify-Review protocol with hooks",
"version": "7.3.0",
"author": {
"name": "paceaitian"
},
"homepage": "https://github.com/paceaitian/paceflow",
"repository": "https://github.com/paceaitian/paceflow",
"license": "MIT",
"keywords": ["workflow", "pace", "hooks", "planning", "artifacts"],
"agents": ["./agents/artifact-writer.md"],
"commands": ["./commands/enable.md", "./commands/disable.md", "./commands/status.md", "./commands/pause.md", "./commands/resume.md"]
}
What it installs
The manifest is a name and a version. 4 skills, 5 commands, 1 agent, 12 hooks travel with it, and installing the plugin installs all of them — 310 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill pace-workflow A 35 tokens
- Skill artifact-management A 36 tokens
- Skill pace-bridge A 38 tokens
- Skill pace-knowledge A 38 tokens
- Command pause A 27 tokens
- Command disable A 19 tokens
- Command enable A 22 tokens
- Command resume A 13 tokens
- Command status A 11 tokens
- Agent artifact-writer A 71 tokens
- Hook PreToolUse A not measured
- Hook SessionStart A not measured
- Hook PostToolUse A not measured
- Hook PostToolUseFailure A not measured
- Hook Notification A not measured
- Hook PreCompact A not measured
- Hook SessionEnd A not measured
- Hook Stop A not measured
- Hook StopFailure A not measured
- Hook SubagentStart A not measured
- Hook SubagentStop A not measured
- Hook UserPromptSubmit A not measured
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 First seen · 15 lines scan A 323b4a25343d
paceflow is a plugin published in the GitHub repository paceaitian/paceflow (38 stars, last pushed 2mo 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-30.
Other plugins, from other repositories
concord-relay
Delivers Concord inter-agent messages into a running Claude Code session, whether it is mid-task or idle at the prompt.
bcc
Breaking Coding Chaos: four dual-loop skills (main + throughline + plan-spar + clean-cut).
gjalla
Production-readiness for your AI coding agents.
skill-router
Skill routing plugin that exposes category routers, keeps leaf skills in a hidden library, and organizes new skills through agent-authored routing plans.
rudder
Maintain a device-local spec from coding-session intent, then generate focused unit tests with your existing coding agent.
agentry
Agentry skill for agent-native analytics, error logging, and deploy attribution over the Agentry HTTP API.