management

management is a skill for Claude Code, Codex from hristo2612/jinn. It costs 18 tokens per session (2,280 once invoked), scanned A, original, MIT.

A workflow for managing an AI organization whose departments, employee roles, and task boards are stored as files. It covers executive, manager, senior, and employee responsibilities.

In plain words
What is it for?
It helps hire or fire employees, create departments, promote or demote people, delegate tasks, review task boards, and reorganize the team.
Why use it?
It provides clear rules for changing team structure and assigning work without losing track of who can manage which people or tasks.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit It helps hire or fire employees, create departments, promote or demote people, delegate tasks, review task boards, and reorganize the team.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/hristo2612/jinn/management
Install

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.

Any agent
npx skills add hristo2612/jinn --skill management
Clone the repo
git clone --depth 1 https://github.com/hristo2612/jinn

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for management

README.md
[![agentmods](https://agentmods.dev/badge/skills/hristo2612/jinn/management/github.svg)](https://agentmods.dev/skills/hristo2612/jinn/management)
Your own site
<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.

agentmods 80×15 button for management

Your own site · 80×15
<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>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,280 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash afef71800927, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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.

packages/jinn/template/migrations/0.26.0/files/base/skills/management/SKILL.md · 227 lines

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 name
  • department - department this employee belongs to (must match parent directory name)
  • rank - one of: executive, manager, senior, employee
  • engine - AI engine to use: claude or codex
  • model - model identifier (e.g., sonnet, opus, o3)
  • persona - multiline description of who this employee is and how they behave
  • reportsTo - (optional) who this employee reports to (employee name)

Auto-determining reportsTo when the user does not specify:

  1. Find the highest-ranked employee in the target department (manager > senior > employee)
  2. If a manager exists → set reportsTo: <manager-name>
  3. If only seniors exist → set reportsTo: <first-senior-alphabetically>
  4. If the department is empty → omit reportsTo (smart defaults attach to root)
  5. Confirm to the user: "Assigned X to report to Y. Change this?"

Read the full file on GitHub · 227 lines

Changes

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.

  1. 9d ago First seen · 227 lines · 18 tokens per session scan A afef71800927

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens