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 agentmods add skills/jackin-project/jackin-dev/jackin-create-prnpx skills add jackin-project/jackin-dev --skill jackin-create-prgit clone --depth 1 https://github.com/jackin-project/jackin-devWrote 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/jackin-project/jackin-dev/jackin-create-pr)<a href="https://agentmods.dev/skills/jackin-project/jackin-dev/jackin-create-pr"><img src="https://agentmods.dev/badge/skills/jackin-project/jackin-dev/jackin-create-pr.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 | $0.00041 | $0.00914 |
| Opus 5 | $0.00020 | $0.00457 |
| Sonnet 5 | $0.00008 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
jackin-create-pr 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 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.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jackin-create-pr
Open a PR for a small fix in the jackin❯ repo — typo, dependency bump, one-line bugfix, doc tweak — that needs no roadmap item. Also the shared PR-mechanics path other skills reuse. Commits inline; no separate commit skill.
jackin❯ rule files auto-load — PULL_REQUESTS.md, .github/ agent rules, BRANCHING.md, COMMITS.md. This skill sequences them, never restates them. Read them for full rules.
When to use
- Operator runs
jackin-create-pr. - Small, self-contained change (no design, no roadmap item).
When NOT to use
- Feature/idea worth a roadmap item →
jackin-propose. - Implementing a finalized roadmap item →
/goal Implement <slug>.md.
Arguments
--branch <name>— explicit branch name.--auto-branch— pick the branch name yourself, no confirmation.--title <msg>— commit + PR title (else derive from the diff, Conventional Commits).
Process
- Branch. Never commit to
main. If onmain, create afix//chore//docs//refactor/-prefixed branch named from the change. Suggest and confirm unless--auto-branchor--branchgiven. - Commit. Uncommitted changes → commit inline per
COMMITS.md: Conventional Commits subject, DCO sign-off (git commit -s). Already committed → skip. Thengit push. - Build the body.
[bin]Runcargo xtask pr body --base origin/main > /tmp/pr-body.md. The classified change digest (rust / docs / capsule / schema + file list) prints to stderr — read it; the body skeleton goes to the file: the PR template (read from.github/PULL_REQUEST_TEMPLATE.mdat runtime) with the verify-locally blocks already selected and byte-exact, prose left as placeholders. Block selection: Checkout + isolation env always; Rust tests on a Rust change; Docs checks + walk ondocs/**; jackin-capsule smoke (with--capsulebefore anyconsole/load) oncrates/jackin-capsule/; schema migration smoke on a versioned-schema touch. - Fill + create.
[agent]Edit/tmp/pr-body.md— write the prose sections (Summary, What ships, Behavior changes) from the digest + diff; drop the optional sections you do not need. Thengh pr create --body-file /tmp/pr-body.md. The binary already wrote the body, so there is no heredoc to quote. - Verify render.
gh pr view <PR> --json body -q .body— confirm the prose you added renders (no stray\`` or$from hand-editing). Fix withgh pr edit --body-file` if needed. - Reply. Share the PR URL and repeat the Verify-locally commands in your final message.
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.
- 4d ago First seen · 51 lines · 41 tokens per session scan A 48ad3f63686e
jackin-create-pr is a skill published in the GitHub repository jackin-project/jackin-dev (3 stars, last pushed 3d ago), licensed Apache-2.0. It adds 41 tokens to every session and 914 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…