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 6529-Collections/6529seize-frontend --skill write-prsgit clone --depth 1 https://github.com/6529-Collections/6529seize-frontendWrote 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/6529-collections/6529seize-frontend/write-prs)<a href="https://agentmods.dev/skills/6529-collections/6529seize-frontend/write-prs"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/write-prs/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/6529-collections/6529seize-frontend/write-prs"><img src="https://agentmods.dev/badge/skills/6529-collections/6529seize-frontend/write-prs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 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 12 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 13 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 16 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 111 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 116 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 121 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.00094 | $0.02370 |
| Opus 5.5 | $0.00038 | $0.00948 |
| Sonnet 5.5 | $0.00019 | $0.00474 |
| Haiku 4.5 | $0.00009 | $0.00237 |
Grade A, and why
write-prs 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.
How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write PRs
Workflow
-
Determine the requested completion mode:
review-ready: create or update the PR and stop once available review bots and the agent are satisfied.merge: do everything inreview-ready, then hand off toops/skills/deploy-6529/SKILL.mdfor merge execution when required checks and approvals allow it.staging: hand off toops/skills/deploy-6529/SKILL.mdfor merge, staging deployment, and health validation. Never prepare, publish, or trigger a release note for staging.prod: hand off toops/skills/deploy-6529/SKILL.mdfor production deployment and health validation. Never author or post a release note; the existing autonomous bot owns production release notes.
If the user did not explicitly request merge or deployment, stop at
review-ready. -
Inspect the change before writing:
- Read the issue, task, or user request.
- Review
git status, the diff, changed files, and relevant tests. - Separate user changes from agent changes; do not revert unrelated work.
- Verify whether docs, generated files, migrations, routes, dependencies, auth, payments, analytics, or deployment-sensitive code are touched.
- For frontend behavior changes, complete E2E Maintenance During Implementation before handoff. Include affected browser specs/packs and the maintenance decision in Validation. For each changed behavioral expectation, identify the user requirement that makes the old expectation obsolete; a changed implementation or failing test alone is not justification. Distinguish reviewed or updated coverage from actual execution and explain any relevant execution gap. A no-wait handoff still requires this inspection and maintenance.
-
Write a concise PR title and body with this format:
## Issue - What problem, user need, bug, or follow-up this PR addresses. ## Fix - The core solution and why it is appropriate. ## Changes - Notable code, docs, config, API, UX, or data-shape changes. ## Validation - Commands, checks, screenshots, E2E runs, or manual flows completed. - Anything intentionally not tested, with the reason and residual risk. ## Risk - Level: Low | Medium | High - Why: blast radius, reversibility, data/security/performance/deploy impact. - Rollback: expected rollback or mitigation path. ## Review Notes - Areas reviewers or bots should focus on, plus any trade-offs.
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 Changed · +9 lines 843761fbdc82
- 1mo ago Changed · +9 lines d485b4983f69
- 1mo ago Changed · +4 lines e4133a633267
- 2mo ago First seen · 126 lines · 94 tokens per session scan A 42067a254318
write-prs is a skill published in the GitHub repository 6529-Collections/6529seize-frontend (10 stars, last pushed today), licensed Apache-2.0. It adds 94 tokens to every session and 2,370 once invoked, about $0.0004 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-31.
Other skills, from other repositories
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.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.