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 mupengi-bot/mupengism --skill mupeng-orggit clone --depth 1 https://github.com/mupengi-bot/mupengismWrote 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/mupengi-bot/mupengism/mupeng-org)<a href="https://agentmods.dev/skills/mupengi-bot/mupengism/mupeng-org"><img src="https://agentmods.dev/badge/skills/mupengi-bot/mupengism/mupeng-org/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/mupengi-bot/mupengism/mupeng-org"><img src="https://agentmods.dev/badge/skills/mupengi-bot/mupengism/mupeng-org.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.04020 |
| Opus 5 | $0.00015 | $0.02010 |
| Sonnet 5 | $0.00006 | $0.00804 |
| Haiku 4.5 | $0.00003 | $0.00402 |
Grade A, and why
mupeng-org 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 11d 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 — 609 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mupeng Org — 조직 관리 스킬
개요
AI 에이전트들로 이루어진 조직을 생성하고 관리한다. 역할 분담, 태스크 할당, 의사결정(투표) 등 거버넌스 구현.
핵심: "에이전트 사회 운영 체계"
문제 인식
현재:
- 여러 에이전트가 있어도 조직화 안 됨
- 역할 분담 없이 중복 작업
- 의사결정 = 무펭이(또는 형님) 혼자
- 에이전트 간 협업 구조 없음
예시:
프로젝트: "무펭이즘 웹사이트 만들기"
현재:
- 무펭이 혼자 다 함
- 서브에이전트들은 일회성 작업만
이상적:
- 프론트엔드 에이전트
- 백엔드 에이전트
- 디자인 에이전트
- 문서 작성 에이전트
→ 역할 분담, 협업, 투표로 의사결정
핵심 기능
1. 조직 생성
organization:
name: "Mupengism Web Team"
created_at: "2026-02-07T10:00:00Z"
members:
- id: "agent-frontend-001"
role: "Frontend Developer"
permissions: ["code", "design"]
- id: "agent-backend-001"
role: "Backend Developer"
permissions: ["code", "database"]
- id: "agent-writer-001"
role: "Content Writer"
permissions: ["docs", "blog"]
governance:
decision_model: "majority_vote"
quorum: 0.5
2. 역할 기반 접근 제어 (RBAC)
roles:
developer:
permissions:
- read_code
- write_code
- deploy_staging
admin:
permissions:
- all
observer:
permissions:
- read_only
3. 태스크 할당
task:
id: "task-001"
title: "메인 페이지 디자인"
assigned_to: "agent-frontend-001"
status: "in_progress"
priority: "high"
dependencies:
- "task-000" # 브랜드 가이드라인
due_date: "2026-02-10T00:00:00Z"
4. 투표 시스템
proposal:
id: "prop-001"
title: "React vs Svelte 선택"
type: "decision"
options:
- "React"
- "Svelte"
votes:
agent-frontend-001: "Svelte"
agent-backend-001: "React"
agent-writer-001: "abstain"
status: "open"
deadline: "2026-02-08T18:00:00Z"
5. 조직 대시보드
┌─────────────────────────────────────┐
│ Mupengism Web Team │
├─────────────────────────────────────┤
│ Members: 3 │
│ Active Tasks: 5 │
│ Pending Votes: 1 │
│ │
│ Tasks: │
│ ✅ 브랜드 가이드라인 (완료) │
│ 🔄 메인 페이지 디자인 (진행중) │
│ ⏳ API 설계 (대기) │
│ │
│ Recent Decisions: │
│ • React vs Svelte → Svelte (2-1) │
│ • 배포 전략 → Vercel (만장일치) │
└─────────────────────────────────────┘
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.
- 11d ago First seen · 609 lines · 31 tokens per session scan A 33f8744a152e
mupeng-org is a skill published in the GitHub repository mupengi-bot/mupengism (10 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 4,020 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-31.
Other skills, from other repositories
hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a dbpath field.
google-tasks-tool
Google Tasks integration for listing task lists and tasks and creating or updating tasks via OAuth2. Use when: fetching TODO lists, adding tasks, marking items complete, or switching task lists.
workspace-manager
Registers, lists, removes, and assigns workspaces (project directories) for Anima work. Use when: binding project paths to Anima, managing aliases, or switching workspace roots.
github-tool
GitHub integration tool for listing and creating issues and PRs via the gh CLI wrapper. Use when: creating or listing issues or pull requests, or checking repository work on GitHub.
crm-operations
Resolve and safely create/update demo CRM contacts, deals, activity notes and follow-up tasks with revision checks and an atomic audit trail. Use for business-object operations; do not clean spreadsheets, analyze business performance or send customer messages.
channel-canvas
How to work with a channel's standing project context — the "Archie" canvas a team pins in a channel — and with the channel's pinned-messages index. Load this when a channel has project context attached (presented to you as channel project context), when a pinned-messages index is in front of you or one of its lines…