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 agentmods add instructions/dropelikeit/pr-comments-resolver/claude-mdgit clone --depth 1 https://github.com/Dropelikeit/pr-comments-resolverWrote 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/dropelikeit/pr-comments-resolver/claude-md)<a href="https://agentmods.dev/instructions/dropelikeit/pr-comments-resolver/claude-md"><img src="https://agentmods.dev/badge/instructions/dropelikeit/pr-comments-resolver/claude-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 | $0.00281 | $0.00281 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
pr-comments-resolver CLAUDE.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 3d 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
PR Comments Resolver — Development Guide
Project Structure
This is a Claude Code skill plugin. The main skill file is skills/resolve-comments/SKILL.md.
.claude-plugin/ Plugin manifests (plugin.json, marketplace.json)
skills/resolve-comments/ The resolve-comments skill
README.md User-facing documentation
CLAUDE.md This file
LICENSE MIT license
Plugin Format
All skill content lives in skills/<skill-name>/SKILL.md. Each SKILL.md requires YAML frontmatter with name, description, and optionally trigger.
The .claude-plugin/plugin.json defines the plugin identity. The .claude-plugin/marketplace.json contains metadata for marketplace distribution.
Conventions
- All
.mdfiles are written in English - SKILL.md frontmatter
descriptionmust start with "Use when..." and describe triggering conditions only (max 500 chars) - Skill names use kebab-case
- This is a multi-skill plugin — future skills go in
skills/<new-skill-name>/SKILL.md
Adding a New Skill
- Create
skills/<skill-name>/SKILL.mdwith the required frontmatter - Follow the existing skill structure (numbered steps, platform-specific branches)
- Update
README.mdto document the new skill
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.
- 3d ago First seen · 33 lines · 281 tokens per session scan A 0a3f1231e843
pr-comments-resolver CLAUDE.md is an instructions file published in the GitHub repository Dropelikeit/pr-comments-resolver (2 stars, last pushed 1mo ago), licensed MIT. It adds 281 tokens to every session, about $0.0014 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-31.
Other instructions, from other repositories
agent-smith CLAUDE.md
Instructions for holgerleichsenring/agent-smith, covering agent-smith — ai agent instructions, context files (read in this order), phase directory structure, experiential memory (remember / recall) and minting a phase id.
claude-code-gauntlet AGENTS.md
Instructions for liatrio-labs/claude-code-gauntlet, covering agents.md, design, tooling boundary (no npm in the tree), scripts and tests.
claude-code-gauntlet CLAUDE.md
Instructions for liatrio-labs/claude-code-gauntlet, covering claude.md and claude code specifics.
agent-orchestrator AGENTS.md
Instructions for geserdugarov/agent-orchestrator, covering repository guide for ai agents, what this project is, where the details live, repository layout and development.
gitchamber AGENTS.md
Instructions for remorses/gitchamber: CLI tool that fetches source code for packages into nodemodules/.gitchamber/ to give coding agents deeper context. Fork of opensrc.
memwiki AGENTS.md
AGENTS.md instructions for hereisSwapnil/memwiki, covering memwiki protocol: agent instructions, 1. session start (reading), 2. during work (synthesizing), 3. session end (updating) and 4. agent slash commands.