Borrowing it
Nothing to install: this file belongs to leshchenko1979/fast-mcp-telegram. 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/leshchenko1979/fast-mcp-telegram/master/.cursor/skills/sourcery-pr-cycle/SKILL.mdgit clone --depth 1 https://github.com/leshchenko1979/fast-mcp-telegramWrote 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/leshchenko1979/fast-mcp-telegram/sourcery-pr-cycle)<a href="https://agentmods.dev/skills/leshchenko1979/fast-mcp-telegram/sourcery-pr-cycle"><img src="https://agentmods.dev/badge/skills/leshchenko1979/fast-mcp-telegram/sourcery-pr-cycle/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/leshchenko1979/fast-mcp-telegram/sourcery-pr-cycle"><img src="https://agentmods.dev/badge/skills/leshchenko1979/fast-mcp-telegram/sourcery-pr-cycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 15 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 123 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 195 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 196 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00073 | $0.01509 |
| Opus 5.5 | $0.00029 | $0.00604 |
| Sonnet 5.5 | $0.00015 | $0.00302 |
| Haiku 4.5 | $0.00007 | $0.00151 |
Grade A, and why
sourcery-pr-cycle 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- sourcery-pr-cycle — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sourcery PR Cycle
End-to-end loop: open PR → Sourcery review → fix → push → re-review → repeat → merge.
For triage and status tables on individual comments, read sourcery-pr-review-analysis. This skill is the workflow loop only.
When to use
- User asks to create a PR or run the Sourcery review cycle
- Post-implementation work is done and the branch needs merge readiness
- Sourcery left comments and the user wants fixes + another review pass
Cycle checklist
Copy and track progress:
PR + Sourcery cycle:
- [ ] 1. Pre-push: exit tests green
- [ ] 2. Create PR (gh push + gh pr create)
- [ ] 3. Wait / poll Sourcery (checks + comments)
- [ ] 4. Triage comments; fix blocking issues
- [ ] 5. Pre-push: exit tests green again
- [ ] 6. Commit + push fixes
- [ ] 7. Request new Sourcery review
- [ ] 8. Repeat 3–7 until clean
- [ ] 9. Closeout + merge when ready
1. Pre-push gate (every push)
Run exit tests/commands from the approved plan before every commit and push. Do not push with failing exits.
If fixes changed behavior, re-run exits after fixes and before commit.
2. Create the PR
Use gh for all GitHub operations. Before creating the PR, gather branch state in parallel:
git status
git diff
git log --oneline -10
git diff main...HEAD # or master — use repo default base
Check whether the branch tracks remote and is up to date.
Push and create (sequential):
git push -u origin HEAD
gh pr create --title "the pr title" --body "$(cat <<'EOF'
## Summary
- ...
## Test plan
- [ ] ...
EOF
)"
Return the PR URL to the user.
Commit rules: Only commit when the user asks. Never commit secrets (.env, tokens, acl.dev.yaml with real bearers).
3. Wait for / check Sourcery
Sourcery runs after the PR exists. Poll until the review finishes or stale.
CI / check status:
gh pr checks <N>
Review comments (issue-level, from sourcery-ai[bot]):
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 202 lines · 73 tokens per session scan A a771c8d581f0
sourcery-pr-cycle is a skill published in the GitHub repository leshchenko1979/fast-mcp-telegram (50 stars, last pushed 8d ago), licensed MIT. It adds 73 tokens to every session and 1,509 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-08-30.
Other skills, from other repositories
pr-reviewer
Review a requested pull request, branch diff or completed task against its actual scope, source and checks. Prepare evidence and comments; post or record a human verdict only when explicitly authorized.
pr-review
Review a GitHub pull request: analyzes changed files to select relevant reviewers, loads project and user memory, runs reviewers in parallel, lets the user pick which findings to post, then submits the review on behalf of the user via gh CLI.
git-hygiene-enforcer
Establishes git workflow guardrails including conventional commits, commit message hooks, branch naming conventions, PR templates, and code review processes. Provides hook configurations, workflow templates, and emergency bypass instructions. Use when users request "setup git hooks", "enforce commit conventions", "add…
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.