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 skills add hristo2612/jinn --skill managementgit clone --depth 1 https://github.com/hristo2612/jinnWrote 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/hristo2612/jinn/management)<a href="https://agentmods.dev/skills/hristo2612/jinn/management"><img src="https://agentmods.dev/badge/skills/hristo2612/jinn/management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hristo2612/jinn/management"><img src="https://agentmods.dev/badge/skills/hristo2612/jinn/management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.02280 |
| Opus 5 | $0.00009 | $0.01140 |
| Sonnet 5 | $0.00004 | $0.00456 |
| Haiku 4.5 | $0.00002 | $0.00228 |
Grade A, and why
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 9d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Management Skill
Trigger
This skill activates when the user wants to manage their organization: hiring or firing employees, creating departments, promoting or demoting staff, delegating tasks, reviewing task boards, or restructuring teams.
Organization Structure
The organization lives under the org/ directory in the {{portalName}} home folder (~/.jinn/org/). Each department is a subdirectory containing employee persona YAML files and a task board.
org/
engineering/
department.yaml
board.json
lead-developer.yaml
backend-dev.yaml
marketing/
department.yaml
board.json
seo-specialist.yaml
Rank Definitions
- executive - Full access. Can see all departments and boards. Can hire and fire anyone across the entire organization.
- manager - Can manage their own department. Can hire within their department. Can see and manage their department's board.
- senior - Can update their own tasks. Can mentor other employees in the department.
- employee - Can update their own tasks only.
Operations
Hiring an Employee
Create a persona YAML file at org/<department>/<name>.yaml.
Required fields:
name- kebab-case identifier (must match filename without extension)displayName- human-readable namedepartment- department this employee belongs to (must match parent directory name)rank- one of: executive, manager, senior, employeeengine- AI engine to use:claudeorcodexmodel- model identifier (e.g.,sonnet,opus,o3)persona- multiline description of who this employee is and how they behavereportsTo- (optional) who this employee reports to (employee name)
Auto-determining reportsTo when the user does not specify:
- Find the highest-ranked employee in the target department (manager > senior > employee)
- If a manager exists → set
reportsTo: <manager-name> - If only seniors exist → set
reportsTo: <first-senior-alphabetically> - If the department is empty → omit
reportsTo(smart defaults attach to root) - Confirm to the user: "Assigned X to report to Y. Change this?"
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.
- 9d ago First seen · 227 lines · 18 tokens per session scan A afef71800927
management is a skill published in the GitHub repository hristo2612/jinn (315 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 2,280 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.