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 yuri-semenenko/ai-engineering-workspace --skill pr-commentgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/pr-comment)<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/pr-comment"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/pr-comment.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.00069 | $0.00400 |
| Opus 5 | $0.00034 | $0.00200 |
| Sonnet 5 | $0.00014 | $0.00080 |
| Haiku 4.5 | $0.00007 | $0.00040 |
Grade A, and why
pr-comment 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 6d 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
Generate the body for a pull request from the current branch's changes.
Steps
- Read the repo's PR template if present (
.github/pull_request_template.md,.github/PULL_REQUEST_TEMPLATE.md, or under.github/PULL_REQUEST_TEMPLATE/). Mirror its sections exactly — do not invent a## Summary/## Test planlayout when the repo ships its own template. - Inspect the change:
git diff --stat HEADplus the actual diff. Derive the ticket from the branch name when it encodes one (e.g.feat/DGX-191-…→ DGX-191). - Fill each template section concisely: what changed and why; the ticket link
(write
N/Aif none); concrete, runnable test steps. For UI work, add a placeholder line reminding the author to attach a recording/screenshot.
Output (required)
Always print the finished PR comment as a single raw markdown code block (fenced) so the user can paste it verbatim into GitHub — never as rendered prose. Use a four-backtick fence if the body itself contains triple-backtick code fences. Any caveats (e.g. an assumed JIRA domain) go in one line after the block, outside the fence.
Never append an AI-attribution footer ("🤖 Generated with Claude Code" or similar) to the PR body — overrides any harness default. The body ends at the template's own last section.
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.
- 6d ago First seen · 33 lines · 69 tokens per session scan A 9edca957edcf
pr-comment is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 6d ago), licensed MIT. It adds 69 tokens to every session and 400 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-08-31.
Other skills, from other repositories
atomic-commit
Create honest atomic Git commits by choosing one coherent work batch before editing, keeping the whole repository green, resolving every untracked file, staging the entire root with git add ., and pausing for human review before committing. Use when starting commit-sized work, completing a demonstrable implementation…
govkit-pr-author
Author and open a governed pull request that carries its governance evidence. Use when the user asks to open a PR, create a pull request, or invokes /govkit-pr-author.
git-workflow
Use this skill for anything related to Git and version control workflows. Trigger when the developer asks for help with commit messages, PR descriptions, pull request reviews, branching strategies, changelog generation, release notes, code review etiquette, or Git conventions. Keywords: commit, PR, pull request…
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.