Borrowing it
Nothing to install: this file belongs to EastStarAI/sanad-agent. 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/EastStarAI/sanad-agent/main/.agents/skills/sanad-pull-request-lifecycle/SKILL.mdgit clone --depth 1 https://github.com/EastStarAI/sanad-agentWrote 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/eaststarai/sanad-agent/sanad-pull-request-lifecycle)<a href="https://agentmods.dev/skills/eaststarai/sanad-agent/sanad-pull-request-lifecycle"><img src="https://agentmods.dev/badge/skills/eaststarai/sanad-agent/sanad-pull-request-lifecycle/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/eaststarai/sanad-agent/sanad-pull-request-lifecycle"><img src="https://agentmods.dev/badge/skills/eaststarai/sanad-agent/sanad-pull-request-lifecycle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00065 | $0.00756 |
| Opus 5 | $0.00032 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
Sanad Pull Request Lifecycle 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sanad Pull Request Lifecycle
Use this skill after work is accepted and scoped. It may prepare local changes and a review handoff, but it must not push, merge, close an Issue, delete a branch, or mutate repository settings without explicit authorization.
Prepare
- Confirm the owning Issue or plan, acceptance criteria, dependencies, and required protected-review labels.
- Search for an existing branch or pull request before creating another.
- Use an isolated worktree for parallel, broad, risky, or review-bound work. Follow the repository's worktree runtime and FVM contracts.
- Read the closest
AGENTS.mdbefore editing and update owning documentation in the same change.
Implement and Verify
- Keep the diff focused and reusable; do not mix unrelated cleanup.
- Add focused tests and run the affected analyzer. Keep verification output bounded while preserving exit status.
- Review the full diff and scan for secrets, personal paths, private infrastructure, generated output, and dependency changes.
- Update the owning task checklist and evidence only after verification.
- Use a Conventional Commits pull-request title. The human PR will be squash merged, so the title must describe the final commit.
- Write the pull request with Problem/Goal, linked
Closes #..., Changes, Verification, risk, cross-platform impact, documentation, and rollback. - Map all modified paths against the repository label taxonomy before creating the pull request. Apply appropriate non-protected category labels such as
type/*andcomp/*only when the taxonomy calls for them. For any required protected positive-review label (maintainer-reviewed,security-reviewed, orrelease-reviewed), report why it is required and ask the responsible maintainer for explicit authorization after presenting the review evidence; never add a protected label merely to make CI pass. If authorization is withheld or unavailable, leave the label absent and report the merge blocker.
Release Delivery Route
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.
- 5d ago Changed · +9 lines · +28 tokens per session 3876255feeaa
- 9d ago First seen · 40 lines · 37 tokens per session scan A 060665dd9a7f
Sanad Pull Request Lifecycle is a skill published in the GitHub repository EastStarAI/sanad-agent (42 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 756 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-30.
Other skills, from other repositories
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
plate
Turn finished local work into a commit, an ordinary pull request, or a pull request stack. Use this skill to commit changes or to publish a branch. Use it to open or update a pull request. Use it to create, sync, restack, or submit a pull request stack. You can also run /plate. This skill owns all staging, commits…
gh-address-comments
Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.
npm
Publish and manage packages on the npm registry (npmjs.com), publish, dist-tags, deprecate, owners, download stats, private installs. Use when the user asks to publish, release or manage an npm package, or to inspect the registry.
mx-pr
Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].
git-authoring
Authors and executes git work end to end — Conventional Commits messages, pull-request content, release notes, and pull-request review, plus the repository operations an engineer runs daily: branching, rebasing, squashing, cherry-picking, reverting, merge-conflict resolution, stashes, tags, remotes, and recovery…