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 darellchua2/opencode-config-template --skill nextjs-pr-workflow-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/nextjs-pr-workflow-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/nextjs-pr-workflow-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/nextjs-pr-workflow-skill.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.00036 | $0.02914 |
| Opus 5 | $0.00018 | $0.01457 |
| Sonnet 5 | $0.00007 | $0.00583 |
| Haiku 4.5 | $0.00004 | $0.00291 |
Grade C, and why
nextjs-pr-workflow-skill scanned grade C with 1 finding 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 4d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
When protocol is enabled, this skill defaults to `Iterations: 10` (sufficient for typical single-pass workflows). Override with `Iterations: N` for specific tasks. Safety blocks: `.env`, `node_modules/`, `rm -rf`, `git p How it starts
The opening of the file, as written. The whole thing — 299 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What I do
I implement a complete Next.js PR creation workflow by extending framework skills:
- Identify Target Branch: Determine which branch PR should merge into (configurable, not hardcoded)
- Run Next.js Quality Checks: Execute
npm run lint,npm run build, andnpm run testusinglinting-workflowframework - Identify Tracking: Check for JIRA tickets or git issue references
- Create Pull Request: Use
pr-creation-workflowframework withgit-semantic-commitsfor PR title formatting - Add JIRA Comments: Use
git-issue-updaterframework for consistent JIRA ticket updates
Critical Requirement: All tests MUST pass (npm run test) before PR creation. This is a blocking step.
When to use me
Use this workflow when:
- Completing implementation of a PLAN.md file
- Finishing new feature implementation in Next.js apps
- Ready to create a PR after development is complete
- Need to ensure code quality before submitting changes
- Following the standard practice of linting, building, and testing before PR
- All tests must pass before PR can be created (blocking requirement)
Governance: This skill follows semantic-release-convention for PR titles, version labels, merge strategy, and release tags (inherited via pr-creation-workflow).
Frameworks Used:
pr-creation-workflow: For PR creation logic and quality checkslinting-workflow: For Next.js linting (npm run lint)jira-git-integration: For JIRA ticket management and comments
Prerequisites
- Next.js project with
npm run lint,npm run build, andnpm run testscripts - Git repository initialized and on a feature branch
- Active Atlassian/JIRA account (if using JIRA integration)
- Write access to repository
- PLAN.md file with implementation details
- All existing tests must pass before using this workflow
Steps
Step 1: Check Project Structure
Verify this is a Next.js project and check for required scripts:
# Verify package.json exists and has required scripts
jq -r '.scripts.lint and .scripts.build and .scripts.test' package.json
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.
- 4d ago First seen · 299 lines · 36 tokens per session scan C 1ec2b5e8c7a5
nextjs-pr-workflow-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 36 tokens to every session and 2,914 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
prowler-changelog
Manages changelog entries for Prowler components following keepachangelog.com format. Trigger: When creating PRs, adding changelog entries, or working with any CHANGELOG.md file in ui/, api/, mcpserver/, or prowler/.
writing-clearly-and-concisely
Apply whenever writing content a human will read — emails, documents, reports, documentation, messages, UI copy, commit messages, explanations, or any other prose. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
qa
QA test your code changes by reading your git diff, choosing the right validation path for frontend/browser and backend changes, and reporting pass/fail with evidence.
finalize
Pre-ship gate — runs detector, verifies brief and tokens, applies the 10-pass finish bar, ranks findings by feedback hierarchy. Use when the user wants to ship, merge, or finalize a surface and needs a verdict (READY / NOT READY / BLOCKED) before committing. Invoke when the user asks for finalize on their UI, or…