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/individual-managementnpx skills add Deepractice/RoleX --skill individual-managementgit clone --depth 1 https://github.com/Deepractice/RoleXWrote 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/deepractice/rolex/individual-management)<a href="https://agentmods.dev/skills/deepractice/rolex/individual-management"><img src="https://agentmods.dev/badge/skills/deepractice/rolex/individual-management.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.00039 | $0.01569 |
| Opus 5 | $0.00019 | $0.00785 |
| Sonnet 5 | $0.00008 | $0.00314 |
| Haiku 4.5 | $0.00004 | $0.00157 |
Grade A, and why
individual-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 5d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Individual Lifecycle Manage the full lifecycle of individuals in the RoleX world. All operations are invoked via the use tool with ! prefix.
Scenario: born — create a new individual Given you want to bring a new individual into the world When you call use with !individual.born Then a new individual node is created under society And the individual can be activated, hired into organizations, and taught skills And parameters are: """ locator: "!individual.born" args: content: "Feature: ..." # Gherkin persona (optional) id: "sean" # kebab-case identifier alias: ["小明", "xm"] # aliases (optional) """
Scenario: born — persona writing guidelines Given the persona defines who this individual is Then the Feature title names the individual And the description captures personality, values, expertise, and background And Scenarios describe distinct aspects of the persona And keep it concise — identity is loaded at every activation
Scenario: retire — archive an individual Given an individual should be temporarily deactivated When you call use with !individual.retire Then the individual is moved to the past archive And all data is preserved for potential restoration via rehire And parameters are: """ locator: "!individual.retire" args: individual: "sean" """
Scenario: die — permanently remove an individual Given an individual should be permanently removed When you call use with !individual.die Then the individual is moved to the past archive And this is semantically permanent — rehire is technically possible but not intended And parameters are: """ locator: "!individual.die" args: individual: "sean" """
Scenario: retire vs die — when to use which Given you need to remove an individual from active duty When the individual may return later (sabbatical, role rotation) Then use retire — it signals intent to restore When the individual is no longer needed (deprecated role, replaced) Then use die — it signals finality
Scenario: rehire — restore a retired individual Given a retired individual needs to come back When you call use with !individual.rehire Then the individual is restored to active society And all previous knowledge, experience, and history are intact And parameters are: """ locator: "!individual.rehire" args: individual: "sean" """
Feature: Knowledge Injection Inject principles and procedures into an individual from the outside. This bypasses the cognition cycle — no encounters or experiences consumed. Use this to equip individuals with pre-existing knowledge and skills.
Scenario: teach — inject a principle Given an individual needs a rule or guideline it hasn't learned through experience When you call use with !individual.teach Then a principle is created directly under the individual And if a principle with the same id already exists, it is replaced (upsert) And parameters are: """ locator: "!individual.teach" args: individual: "sean" content: "Feature: Always validate input\n ..." id: "always-validate-input" """
Scenario: train — inject a procedure (skill reference) Given an individual needs a skill it hasn't mastered through experience When you call use with !individual.train Then a procedure is created directly under the individual And if a procedure with the same id already exists, it is replaced (upsert) And the procedure Feature description MUST contain the ResourceX locator for the skill And parameters are: """ locator: "!individual.train" args: individual: "sean" content: "Feature: Skill Creator\n https://github.com/Deepractice/DeepracticeX/tree/main/skills/skill-creator\n\n Scenario: When to use\n Given I need to create a skill\n Then load this skill" id: "skill-creator" """
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.
- 5d ago First seen · 171 lines · 39 tokens per session scan A c67b1916df3e
individual-management is a skill published in the GitHub repository Deepractice/RoleX (35 stars, last pushed 5mo ago), licensed MIT. It adds 39 tokens to every session and 1,569 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.
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…