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/vybestack/llxprt-code/llxprt-issue-workflownpx skills add vybestack/llxprt-code --skill llxprt-issue-workflowgit clone --depth 1 https://github.com/vybestack/llxprt-codeWrote 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/vybestack/llxprt-code/llxprt-issue-workflow)<a href="https://agentmods.dev/skills/vybestack/llxprt-code/llxprt-issue-workflow"><img src="https://agentmods.dev/badge/skills/vybestack/llxprt-code/llxprt-issue-workflow.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.00087 | $0.02074 |
| Opus 5 | $0.00044 | $0.01037 |
| Sonnet 5 | $0.00017 | $0.00415 |
| Haiku 4.5 | $0.00009 | $0.00207 |
Grade A, and why
llxprt-issue-workflow 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 6d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LLxprt Issue Workflow
End-to-end workflow for taking a GitHub issue in this repository from intake to a green, review-clean pull request.
1. Setup
- Checkout main and pull latest from origin. Do NOT delete any files or run
git clean— justgit checkout main && git pull. - Create branch
issueNUM(e.g.issue1234). - Use
ghto pull the issue and its comments, AND assign the issue to acoliver:gh issue edit NUM --add-assignee acoliver. - Always use
ghfor issues/PRs/comments — never webfetch. Use proper gh command syntax and avoid unescaped backticks in bodies/comments (they trigger shell command substitution).
2. Research and plan
- Research the issue in the codebase using the description and comments as the starting point.
- Create a test-first plan following dev-docs/RULES.md behavioral tests (no mock
theater). See the
typescript-test-writingskill for the distilled test rules. - Plan documents go in
project-plans/, NEVER indev-docs/. dev-docs/ holds durable engineering reference material (PLAN.md, RULES.md, architecture notes); project-plans/ holds per-issue and per-feature planning. Writing a plan to dev-docs/plans/ is wrong — dev-docs/PLAN.md and dev-docs/PLAN-TEMPLATE.md are the methodology you follow, not the destination you write to. This is enforced by scripts/check-doc-placement.ts, which fails if dev-docs/plans/ exists. - Temporary issue state belongs under project-plans/, not dev-docs/.
Scope rules
- Scope is based on functionality, not line counts. Never add line or file counts for issue scope; if an issue contains them, ignore them.
- Do not update unrelated project-plan files owned by other issue efforts except when required to resolve conflicts or unblock the current PR. CI, lint, test, and formatting failures automatically authorize bounded scope expansion needed to make the PR green; do not ask for approval based only on file or line counts. Ask only before major functional or architectural expansions beyond the issue scope.
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.
- 6d ago First seen · 168 lines · 87 tokens per session scan A a96239f52c40
llxprt-issue-workflow is a skill published in the GitHub repository vybestack/llxprt-code (700 stars, last pushed today), licensed Apache-2.0. It adds 87 tokens to every session and 2,074 once invoked, about $0.0004 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…