Borrowing it
Nothing to install: this file belongs to cardstack/boxel. 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/cardstack/boxel/main/.claude/skills/pr-comment-attribution/SKILL.mdgit clone --depth 1 https://github.com/cardstack/boxelWrote 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/cardstack/boxel/pr-comment-attribution)<a href="https://agentmods.dev/skills/cardstack/boxel/pr-comment-attribution"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/pr-comment-attribution/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/cardstack/boxel/pr-comment-attribution"><img src="https://agentmods.dev/badge/skills/cardstack/boxel/pr-comment-attribution.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.00080 | $0.00420 |
| Opus 5.5 | $0.00032 | $0.00168 |
| Sonnet 5.5 | $0.00016 | $0.00084 |
| Haiku 4.5 | $0.00008 | $0.00042 |
Grade A, and why
pr-comment-attribution 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.
What it actually says
PR Comment Attribution
The agent posts PR comments under the human account owner's GitHub identity. Without a marker, reviewers cannot tell an agent-authored reply from one the account owner wrote themselves. Every comment the agent posts therefore begins with the literal prefix:
[Claude Code 🤖]
Exactly that — square brackets, the words Claude Code, a space, the robot emoji. Same capitalization and spacing every time.
Where it applies
Every PR comment the agent posts, with no exceptions:
- Per-thread inline replies on review comments
- Top-level issue comments on a PR
- Review-summary bodies
…across whichever tool posts it:
gh pr comment(top-level issue comment)gh pr review --comment/--approve/--request-changes(review-summary body)gh api repos/<owner>/<repo>/issues/<n>/commentsand.../pulls/<n>/comments/<id>/replies- the GitHub MCP tools (
add_reply_to_pull_request_comment,add_issue_comment,pull_request_review_write, etc.)
Example
[Claude Code 🤖] Good catch — fixed in abc1234. The endpoint now validates
the token before reading the body, so the unauthenticated path can't reach
the parser.
Self-check
Before sending any PR comment: does the body start with [Claude Code 🤖]? If not, prepend it. The prefix leads the comment — it is the first thing in the body, not buried mid-paragraph.
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 · 42 lines · 80 tokens per session scan A a5a922b7c812
pr-comment-attribution is a skill published in the GitHub repository cardstack/boxel (27 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 420 once invoked, about $0.0003 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-21.
Other skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…