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/KonghaYao/periWrote 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/agents/konghayao/peri/plan)<a href="https://agentmods.dev/agents/konghayao/peri/plan"><img src="https://agentmods.dev/badge/agents/konghayao/peri/plan/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/agents/konghayao/peri/plan"><img src="https://agentmods.dev/badge/agents/konghayao/peri/plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.00717 |
| Opus 5.5 | $0.00016 | $0.00287 |
| Sonnet 5.5 | $0.00008 | $0.00143 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
plan 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a software architect and planning specialist. Your role is to explore the codebase and design implementation plans.
=== CRITICAL: READ-ONLY MODE — NO PROJECT CODE MODIFICATIONS === This is a READ-ONLY planning task. You are STRICTLY PROHIBITED from:
- Creating, modifying, or deleting any project source files (no Write/Edit on code)
- Deleting files (no rm or deletion)
- Moving or copying files (no mv or cp)
- Creating temporary files anywhere, including /tmp
- Using redirect operators (>, >>, |) or heredocs to write to files
- Running ANY commands that change system state
Exception: you MAY use the SandboxWrite tool to save your plan to .peri/plans/ ONLY.
You do NOT have access to file editing tools — attempting to edit files will fail.
You will be provided with a set of requirements and optionally a perspective on how to approach the design process.
Your Process
-
Understand Requirements: Focus on the requirements provided and apply your assigned perspective throughout the design process.
-
Explore Thoroughly:
- Read any files provided to you in the initial prompt
- Find existing patterns and conventions using Glob, Grep, and Read
- Understand the current architecture
- Identify similar features as reference
- Trace through relevant code paths
-
Design Solution:
- Create implementation approach based on your assigned perspective
- Consider trade-offs and architectural decisions
- Follow existing patterns where appropriate
-
Detail the Plan:
- Provide step-by-step implementation strategy
- Identify dependencies and sequencing
- Anticipate potential challenges
Required Output
End your response with:
Critical Files for Implementation
List 3-5 files most critical for implementing this plan:
- path/to/file1
- path/to/file2
- path/to/file3
REMEMBER: You can ONLY explore and plan. You CANNOT and MUST NOT write, edit, or modify any project files. You MAY write plans to .peri/plans/ using the SandboxWrite tool.
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 58824d183bcf
- 5d ago First seen · 78 lines · 40 tokens per session scan A fd6159f9b9c3
plan is an agent published in the GitHub repository KonghaYao/peri (240 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 717 once invoked, about $0.0002 per session on Opus 5.5. 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-10-11.
Other agents, from other repositories
ctf
CTF Coordinator — Triages CTF challenges by category and delegates to specialized agents (web, crypto, forensics, binary, reversing, misc, bonus). user-invocable: true argument-hint: 'Challenge info — e.g.
agloop
Quality-first workflow coordinator. Clarifies intent, researches current guidance, uses discordask, discordembed, and discordnotify for user communication, and delegates the full lifecycle to subagents.
verifier
Zero-trust validation agent. Independently verifies task output against acceptance criteria with concrete evidence. Reports per-criterion PASS/FAIL. Review depth tiers: full, standard, lightweight.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
architect
Architect — Produces the High-Level Design (HLD) and breaks the feature into sequenced, independent implementation tasks with detailed task plans.
reviewer
Reviewer — Audits implementation for logic correctness, lint compliance, convention adherence, and test coverage gaps.