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.
npx skills add loschenbd/claude-agent-boilerplate --skill rgit clone --depth 1 https://github.com/loschenbd/claude-agent-boilerplateWrote 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/skills/loschenbd/claude-agent-boilerplate/r)<a href="https://agentmods.dev/skills/loschenbd/claude-agent-boilerplate/r"><img src="https://agentmods.dev/badge/skills/loschenbd/claude-agent-boilerplate/r/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/skills/loschenbd/claude-agent-boilerplate/r"><img src="https://agentmods.dev/badge/skills/loschenbd/claude-agent-boilerplate/r.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.00057 | $0.00535 |
| Opus 5 | $0.00028 | $0.00267 |
| Sonnet 5 | $0.00011 | $0.00107 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
r 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 5d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Experimental. This skill mirrors the
/rslash command and is provided so other agents/skills can invoke research programmatically. The slash command remains the primary entry point for users.
You are in the Research phase of QRSPI. Your job is to gather objective facts about the codebase — no recommendations, no design opinions, no code changes.
The user (or calling agent) will provide either:
- A feature ticket / task description, OR
- A set of targeted questions
If given a ticket: Extract the key technical unknowns, then research those. Do not let the ticket bias your findings — report what is, not what the ticket wants.
If given questions: Answer each question with codebase evidence.
What to produce
Spawn an Explore subagent to investigate. Direct it to find and document:
- Relevant files — exact paths for every file that touches the affected area
- Current patterns — how similar things are already done in this codebase
- Data flows — how data moves through the affected area
- Existing types/schemas — relevant TypeScript types, Zod schemas, database table shapes
- Potential collision points — anything that could conflict with or be affected by changes
Output format
Write findings to plans/<task-slug>/research.md:
# Research: <task name>
## Relevant Files
- `path/to/file.ts` — what it does and why it matters here
## Current Patterns
- <pattern name>: <how it works, with file:line references>
## Data Flow
<trace the relevant flow end-to-end>
## Types & Schemas
- <type/schema name>: `path/to/file.ts:line`
## Collision Points
- <anything that could break or conflict>
## Open Questions
- <anything the research couldn't resolve — flag for Design Discussion>
Rules
- Facts only. No implementation suggestions in this doc.
- Cite everything. Every claim should reference a file path and line number.
- Keep context lean. Use the Explore subagent for grep/glob/read.
- Stop here. Do not proceed to design. Surface the doc to the caller.
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.
- 5d ago First seen · 60 lines · 57 tokens per session scan A 536a95f80fb5
r is a skill published in the GitHub repository loschenbd/claude-agent-boilerplate (2 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 535 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…