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/prototype-managementnpx skills add Deepractice/RoleX --skill prototype-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.00024 | $0.00392 |
| Opus 5 | $0.00012 | $0.00196 |
| Sonnet 5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
prototype-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 2d 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.
What it actually says
Feature: Prototype Registry Register and unregister prototypes. A prototype is an instruction set (prototype.json + .feature files) that materializes roles, organizations, and positions in the runtime when settled.
Scenario: settle — execute a prototype into the world Given you have a ResourceX source (local path or locator) containing a prototype When you call use with !prototype.settle Then the prototype.json is loaded and all @filename references are resolved And each instruction is executed in order against the runtime And the prototype id and source are registered in the prototype registry And parameters are: """ locator: "!prototype.settle" args: source: "./prototypes/rolex"
# or by registry locator:
locator: "!prototype.settle"
args:
source: "deepractice/rolex"
"""
Scenario: evict — remove a prototype from the registry Given a prototype is no longer needed When you call use with !prototype.evict Then the id is removed from the prototype registry And runtime entities created by the prototype are NOT removed And parameters are: """ locator: "!prototype.evict" args: id: "rolex" """
Scenario: Settle is idempotent Given a prototype has already been settled When settle is called again with the same source Then existing entities are skipped (all ops check for duplicate ids) And the result is identical to the first settle
Scenario: Auto-born on activate Given a prototype is registered but no runtime individual exists When activate is called with the individual's id Then the individual is automatically born from the prototype
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.
- 2d ago First seen · 51 lines · 24 tokens per session scan A da263be92d41
prototype-management is a skill published in the GitHub repository Deepractice/RoleX (35 stars, last pushed 5mo ago), licensed MIT. It adds 24 tokens to every session and 392 once invoked, about $0.0001 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…