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 serejaris/personal-corp-os --skill managergit clone --depth 1 https://github.com/serejaris/personal-corp-osWrote 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/serejaris/personal-corp-os/manager)<a href="https://agentmods.dev/skills/serejaris/personal-corp-os/manager"><img src="https://agentmods.dev/badge/skills/serejaris/personal-corp-os/manager/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/serejaris/personal-corp-os/manager"><img src="https://agentmods.dev/badge/skills/serejaris/personal-corp-os/manager.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium analysis-evasion · line 1 Suspicious Unicode normalization or mixed-script contentFix: Review the flagged content for security risks. Ensure no credentials, secrets, or sensitive data are exposed.
- medium Agent Snooping · line 187 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00063 | $0.06038 |
| Opus 5 | $0.00032 | $0.03019 |
| Sonnet 5 | $0.00013 | $0.01208 |
| Haiku 4.5 | $0.00006 | $0.00604 |
Grade A, and why
manager 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manager — двусторонний мост между сессией и GitHub issues
Железные инварианты — читать первым, повторять перед каждым синком
1-3 обязательны для любого issue, который трогает manager. 4-5 добавляются для активного issue текущей недели. 6-9 действуют в режиме записи и при закрытии.
- W-label — текущая неделя, будущая неделя или дата конкретной менторской сессии. Нет в репо — создать.
- Родительский эпик — ровно один parent через GitHub Sub-issues API. Всё, что не эпик само, имеет parent. Подробно: reference/parent-epic-rules.md.
- Трек различается по title + членству в эпике — track-labels (
x26-bloom,ai-native-s2и т.п.) больше не заводим. - Project placement — активный issue текущей недели стоит на канонической GitHub Project-доске своего слоя и в глобальном недельном Project
ris © corp/ Project#4. W-label без Project placement =Расхождение Project. - Родитель виден в Project — для активного child одного
parent_issue_urlмало. Видимый parent/root эпик тоже должен быть в нужном Project view с непустой status lane. - Комментарий-запись о работе (режим записи, только при РЕАЛЬНОЙ работе по issue) — GitHub-комментарий в таймлайне: что сделано + ссылки на коммиты. Смена status/label/Project placement его не заменяет. Чисто механический re-label или Project-fix — без комментария.
- Дробность задач: никакого чат-журнала — если по треку появилось больше одного самостоятельного следующего шага или founder говорит, что за ходом тяжело следить, не превращать один issue в длинный журнал. Parent/track issue держит короткий канон:
Status,Next issues,Decisions. Исполняемые шаги выносить в отдельные child/sibling issues под тем же эпиком — с W-label, Project placement и понятным критерием готовности. - Чек-лист закрытия — закрывать issue можно, только когда: (а) нерешённые развилки и секция «Открыто» из тела перенесены в отдельный открытый issue; (б) каждый follow-up с датой вписан в
tasks/WNN/<дата>.mdсвоей даты; (в) параллельные открытые issues того же контура закрыты комментом-указателем «продолжение в #N» либо оставлены открытыми с причиной. - Переход «нетронута → In progress» и запись предложений/драфтов в issue — при создании задача находится в статусе
Backlog/ Untouched (не тронута). Как только по задаче появилось первое предложение, черновик текста, драфт поста, спецификация или решение:- Статус задачи (в Project и body) ОБЯЗАТЕЛЬНО переводится в
In progress. - Само подготовленное предложение/драфт/спецификация записывается прямо в тело задачи (в
## Proposed draft / solutionили## Updates), чтобы наработки и варианты не терялись в чате сессии.
- Статус задачи (в Project и body) ОБЯЗАТЕЛЬНО переводится в
What ships with it
22 files 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.
- assets/illustration.png 476 KB
- process-logs/2026-05-29-label-drift-six-agent.md 10 KB
- process-logs/2026-05-29-mentoring-routing-six-agent.md 8.6 KB
- process-logs/2026-05-30-kruzhok-russian-title-gate.md 9.5 KB
- process-logs/2026-05-30-kruzhok-task-hierarchy-six-agent-recheck-2.md 6.1 KB
- process-logs/2026-05-30-kruzhok-task-hierarchy-six-agent.md 5.8 KB
- process-logs/2026-05-30-kruzhok-title-prefix-removal-recheck.md 5.8 KB
- process-logs/2026-05-30-related-tasks-hq-drift-six-agent.md 7.9 KB
- process-logs/2026-06-10-gh-query-optimization.md 1.1 KB
- process-logs/2026-06-17-graphql-jq-bypass-fix.md 3.1 KB
- process-logs/2026-06-25-project4-orphan-triage.md 20 KB
- process-logs/triage-decisions.jsonl 33 KB
- README.md 6.7 KB
- README.ru.md 9.5 KB
- reference/issue-authoring.md 18 KB
- reference/kruzhok-hierarchy.md 7.6 KB
- reference/modes-read-write.md 17 KB
- reference/parent-epic-rules.md 12 KB
- reference/project-sync.md 11 KB
- reference/search-algorithm.md 16 KB
- templates/issue-body-templates.md 6.0 KB
- templates/kruzhok-product-task-hierarchy.md 12 KB
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 · 276 lines · 63 tokens per session scan A b6385c876605
manager is a skill published in the GitHub repository serejaris/personal-corp-os (224 stars, last pushed 13d ago), licensed MIT. It adds 63 tokens to every session and 6,038 once invoked, about $0.0003 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
milestone-runner
Use when asked to "run milestones", "execute EXECUTIONPROMPTS.md", "continue the milestone sequence", "run independent milestones in parallel", "merge the stack", or "reconcile M5" after prior work changes the current design. Not for generating plan files; use plan-prompts. Not for repairing one stack; use stacked-prs.
task-decomposer
Produces phased task boards from feature requests: dependency-mapped work items, parallelization flags, risk flags, edge cases, test matrices. Triggers on: "decompose this feature", "task breakdown with dependencies", "phased implementation plan", "work breakdown structure". NOT for discovering which decisions are…
project-context-setup
Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…
github
GitHub CLI operations via gh for issues, PRs, Actions, releases, and REST/GraphQL API with --json/--jq parsing. Triggers on: "create an issue", "submit a PR", "check CI status", "why did CI fail", "merge a PR", or pasted GitHub URLs.
slack
Slack workspace integration: 9 on-demand scripts (post, read, delete, search, stream, react, upload, channels, users) + dual-token support + RTS API search + chat streaming + AI Block Kit + Session Bridge + Claudicle unified launcher (Claude Agent SDK, soul engine, three-tier memory).
mx-flow
Full development workflow orchestrator: brainstorm → plan → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a feature or significant change from scratch. Usage: /mx-flow ; /mx-flow status [name]; /mx-flow finish .