Borrowing it
Nothing to install: this file belongs to bostonaholic/rpikit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bostonaholic/rpikit/main/AGENTS.mdgit clone --depth 1 https://github.com/bostonaholic/rpikitWrote 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/instructions/bostonaholic/rpikit/agents-md)<a href="https://agentmods.dev/instructions/bostonaholic/rpikit/agents-md"><img src="https://agentmods.dev/badge/instructions/bostonaholic/rpikit/agents-md.svg" alt="Measured on agentmods" 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.00957 | $0.00957 |
| Opus 5 | $0.00478 | $0.00478 |
| Sonnet 5 | $0.00191 | $0.00191 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
rpikit AGENTS.md 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 8d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
This file provides guidance to AI coding assistants when working with code in this repository.
Project Overview
rpikit is a Claude Code plugin implementing the Research-Plan-Implement (RPI) framework. It enforces disciplined software engineering through structured workflows with human approval gates between phases.
Architecture & Components
See docs/architecture.md for the full component model, skill/agent tables, delegation map, and design principles.
Workflow: /rpikit:research-plan-implement runs the full pipeline, or use individual skills:
/rpikit:researching-codebase → (approval) → /rpikit:writing-plans → (approval) →
/rpikit:implementing-plans
Development
See CONTRIBUTING.md for setup commands, git hooks, development workflow, component conventions, and releasing.
Git Workflow
- No pull requests. Commits go directly to main locally.
- No merge commits. Always use squash or rebase to keep history linear. When integrating a worktree branch, decide: squash if the branch has messy/WIP commits, rebase if each commit is clean and meaningful.
- Branches may be created when using worktrees for isolation during development, but the end result is a squash or rebase onto main — never a merge commit.
- This facilitates agentic workflows that validate their own changes without requiring full code reviews.
Changelog Rules
CHANGELOG.md tracks plugin user-facing changes only — features, skills, agents, commands, and behaviors that ship to users who install rpikit. Never log local development tooling, CI config, or repo-internal conveniences (e.g., local slash commands, dev scripts) as changelog entries.
Documentation Requirements
README.md is updated only during release prep — never between releases. The README is the primary user-facing
documentation and must match what marketplace users have installed. After changes that affect user-visible behavior,
update CHANGELOG.md's [Unreleased] section instead. At release time, batch-update the README to reflect all
accumulated changes.
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.
- 8d ago First seen · 110 lines · 957 tokens per session scan A 184feedac26c
rpikit AGENTS.md is an instructions file published in the GitHub repository bostonaholic/rpikit (20 stars, last pushed today), licensed MIT. It adds 957 tokens to every session, about $0.0048 per session on Opus 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-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.