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/organization-managementnpx skills add Deepractice/RoleX --skill organization-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/organization-management)<a href="https://agentmods.dev/skills/deepractice/rolex/organization-management"><img src="https://agentmods.dev/badge/skills/deepractice/rolex/organization-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 | $0.00024 | $0.01454 |
| Opus 5 | $0.00012 | $0.00727 |
| Sonnet 5 | $0.00005 | $0.00291 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
organization-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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Organization Lifecycle Manage the full lifecycle of organizations in the RoleX world. Organizations group individuals via membership and can have a charter.
Scenario: found — create an organization Given you want to create a new organization When you call use with !org.found Then a new organization node is created under society And individuals can be hired into it And a charter can be defined for it And parameters are: """ locator: "!org.found" args: content: "Feature: Deepractice\n An AI agent framework company" id: "dp" alias: ["deepractice"] # optional """
Scenario: charter — define the organization's mission Given an organization needs a formal mission and governance When you call use with !org.charter Then the charter is stored under the organization And parameters are: """ locator: "!org.charter" args: org: "dp" content: "Feature: Build great AI\n Scenario: Mission\n Given we believe AI agents need identity\n Then we build frameworks for role-based agents" """
Scenario: dissolve — dissolve an organization Given an organization is no longer needed When you call use with !org.dissolve Then the organization is archived to past And parameters are: """ locator: "!org.dissolve" args: org: "dp" """
Feature: Membership Manage who belongs to an organization. Membership is a link between organization and individual.
Scenario: hire — add a member Given an individual should join an organization When you call use with !org.hire Then a membership link is created between the organization and the individual And the individual can then be appointed to positions And parameters are: """ locator: "!org.hire" args: org: "dp" individual: "sean" """
Scenario: fire — remove a member Given an individual should leave an organization When you call use with !org.fire Then the membership link is removed And parameters are: """ locator: "!org.fire" args: org: "dp" individual: "sean" """
Feature: Position Lifecycle Manage the full lifecycle of positions in the RoleX world. Positions are independent entities that can be charged with duties and linked to individuals via appointment.
Scenario: establish — create a position Given you want to define a new role or position When you call use with !position.establish Then a new position entity is created under society And it can be charged with duties and individuals can be appointed to it And parameters are: """ locator: "!position.establish" args: content: "Feature: Backend Architect\n Responsible for system design and API architecture" id: "architect" """
Scenario: charge — assign a duty to a position Given a position needs specific responsibilities defined When you call use with !position.charge Then a duty node is created under the position And individuals appointed to this position inherit the duty And parameters are: """ locator: "!position.charge" args: position: "architect" content: "Feature: Design systems\n Scenario: API design\n Given a new service is needed\n Then design the API contract first" id: "design-systems" """
Scenario: require — declare a required skill for a position Given a position requires individuals to have specific skills When you call use with !position.require Then a requirement node is created under the position And individuals appointed to this position will automatically receive the skill And upserts by id — if the same id exists, it replaces the old one And parameters are: """ locator: "!position.require" args: position: "architect" content: "Feature: System Design\n Scenario: When to apply\n Given a new service is planned\n Then design the architecture before coding" id: "system-design" """
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 · 187 lines · 24 tokens per session scan A f88638907148
organization-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 1,454 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.
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…