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/dodobrands/PeekieWrote 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/dodobrands/peekie/agent)<a href="https://agentmods.dev/plugins/dodobrands/peekie/agent"><img src="https://agentmods.dev/badge/plugins/dodobrands/peekie/agent/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/dodobrands/peekie/agent"><img src="https://agentmods.dev/badge/plugins/dodobrands/peekie/agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
peekie 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": "peekie",
"version": "1.0.0",
"description": "Teaches the agent when and how to reach for the peekie CLI (tests/warnings/errors/coverage subcommands)",
"author": {
"name": "Aleksey Berezka"
},
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 6 skills travel with it, and installing the plugin installs all of them — 548 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.
- 1mo ago First seen · 10 lines scan A 208343f7b904
peekie is a plugin published in the GitHub repository dodobrands/Peekie (32 stars, last pushed 4d 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
swift-testing-expert
Expert Swift Testing guidance for test structure, #expect/#require usage, traits and tags, parameterized tests, async waiting patterns, parallel execution, and XCTest migration.
craft
Full-stack developer toolkit with integrated workflow automation - 48 commands, 2 agents, 41 skills with standardized dry-run preview mode (29 with --dry-run support). Code, git, site, docs, testing, architecture, CI, distribution, teaching workflows, planning, release pipeline, and ADHD-friendly features including…
vitest-auto-spy
Typed test spies from a class or a type on Vitest, bun:test and node:test — the skill teaches an agent the API, the anti-patterns, the error→fix table and the codemod that migrates a suite off jest-auto-spies or jasmine-auto-spies.
sdlc
Software Development Lifecycle standards and requirements for project quality, security, and compliance.
preflight
Multi-agent CI/CD pipeline ensuring Python packages pass cross-platform, multi-version, and quality gates before shipping to GitHub or PyPI.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.