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/deepractice/rolex/issue-managementnpx skills add Deepractice/RoleX --skill issue-managementgit clone --depth 1 https://github.com/Deepractice/RoleXWhat 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.00035 | $0.01346 |
| Opus 5 | $0.00017 | $0.00673 |
| Sonnet 5 | $0.00007 | $0.00269 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
issue-management 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 3d 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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: IssueX Concepts IssueX is the issue tracking system for RoleX individuals. It follows the GitHub Issues model — issues, comments, and labels. Issues enable structured asynchronous communication between individuals.
Scenario: What is an issue Given an issue is a titled piece of structured communication Then it has a number (auto-increment, like GitHub #1 #2) And it has a title, body, status (open/closed), author, and optional assignee And it can have labels for categorization And it can have comments for threaded discussion
Scenario: Author is the active role Given the author field identifies which individual published the issue When using issue commands through a role Then the author should be the active individual's id
Feature: Issue Lifecycle Commands Commands for creating, viewing, updating, and closing issues.
Scenario: Publish a new issue Given I need to create a new issue When I call use with !issue.publish Then a new issue is created with auto-incremented number And status defaults to "open" And optional: assignee can be set at creation And parameters are: """ locator: "!issue.publish" args: title: "Issue title" body: "Issue description" author: "individual-id" assignee: "other-id" # optional """
Scenario: Get issue details Given I need to view a specific issue When I call use with !issue.get Then the full issue is returned including labels And parameters are: """ locator: "!issue.get" args: number: 1 """
Scenario: List issues with filters Given I need to browse issues When I call use with !issue.list Then matching issues are returned ordered by number descending And all filter parameters are optional — omit for all issues And parameters are: """ locator: "!issue.list" args: status: "open" # optional author: "id" # optional assignee: "id" # optional label: "bug" # optional """
Scenario: Update an issue Given I need to change an issue's title, body, or assignee When I call use with !issue.update Then the specified fields are updated And parameters are: """ locator: "!issue.update" args: number: 1 title: "New title" # optional body: "New body" # optional assignee: "id" # optional """
Scenario: Close an issue Given an issue is resolved When I call use with !issue.close Then status changes to "closed" and closedAt is set And parameters are: """ locator: "!issue.close" args: number: 1 """
Scenario: Reopen an issue Given a closed issue needs more work When I call use with !issue.reopen Then status changes back to "open" and closedAt is cleared And parameters are: """ locator: "!issue.reopen" args: number: 1 """
Scenario: Assign an issue Given I need to assign an issue to another individual When I call use with !issue.assign Then the issue's assignee is updated And parameters are: """ locator: "!issue.assign" args: number: 1 assignee: "individual-id" """
Feature: Comment Commands Commands for adding and viewing comments on issues.
Scenario: Add a comment Given I want to discuss an issue When I call use with !issue.comment Then a comment is added to the issue And parameters are: """ locator: "!issue.comment" args: number: 1 body: "Comment text" author: "individual-id" """
Scenario: List comments Given I want to see the discussion on an issue When I call use with !issue.comments Then all comments are returned ordered by creation time And parameters are: """ locator: "!issue.comments" args: number: 1 """
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.
- 3d ago First seen · 188 lines · 35 tokens per session scan A 22a4ebe7ce08
issue-management is a skill published in the GitHub repository Deepractice/RoleX (35 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,346 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…