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 ngocsangyem/MeowKit --skill project-organizationgit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/project-organization)<a href="https://agentmods.dev/skills/ngocsangyem/meowkit/project-organization"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/project-organization/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/ngocsangyem/meowkit/project-organization"><img src="https://agentmods.dev/badge/skills/ngocsangyem/meowkit/project-organization.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.00039 | $0.01190 |
| Opus 5 | $0.00019 | $0.00595 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
mk:project-organization 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Organization
Standardize file locations, naming conventions, and directory structure for projects.
When to Use
- Creating a file and need the correct path
- Organizing existing files after a messy session
- Enforcing naming conventions across the project
- Other skills need to know where to save output (advisory mode)
Explicit: /mk:project-organization [targets]
Workflow Integration
Operates in Phase 6 (Reflect) or advisory mode (called by any skill). Output supports the documenter agent.
Modes
| Mode | Trigger | Behavior |
|---|---|---|
| Advisory | Other skills reference this skill | Return correct path + naming for file type |
| Organize | User invokes directly | Scan → propose → confirm → execute |
Process (Organize Mode)
- Scan + categorize — list all files, assign each to directory category per
references/directory-rules.md, check naming conventions - Propose — present changes as from → to table, ask user approval
- Execute + report — move/rename files, create missing directories, list final structure
Process (Advisory Mode)
- Determine file type from context (source? doc? plan? test? asset?)
- Look up correct path from directory categories
- Apply naming rules (timestamped / evergreen / variant)
- Return:
{path}/{name}.{ext}
Output Format
## Project Organization: {scope}
**Mode:** {advisory | organize}
**Files scanned:** {N}
**Issues found:** {N}
### Changes
| From | To | Reason |
|------|------|--------|
| {old path} | {new path} | {rule violated} |
### Final Structure
{tree view of organized directories}
References
| Reference | When to load | Content |
|---|---|---|
| directory-rules.md | Steps 2-4 — categorizing + naming | Directory categories, naming patterns, nesting logic |
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.
- 9d ago First seen · 106 lines · 39 tokens per session scan A 579220f556dd
mk:project-organization is a skill published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,190 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-09-03.
Other skills, from other repositories
n8n-pto-pipeline
Create n8n workflow for daily task assignment from PTO engineer to foreman via Telegram bot with status reporting.
daily-brief
Surfaces recent updates relevant to you from GitHub, Linear, Slack, and other configured sources — PR reviews, new assignments, ticket changes, mentions, and CI failures. Use when starting work, catching up after being away, or prepping for standup.
gws-workflow-standup-report
Google Workflow: Today's meetings + open tasks as a standup summary.
pm
When you want to manage projects across your businesses using a kanban + Eisenhower methodology. One kanban per business (whatever portfolio of businesses, projects, or initiatives you run). Tool-agnostic — connects via API/MCP to whatever PM tool each business uses (Notion, GitHub Projects, Plane, Linear, Obsidian…
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
work
Execute Elixir/Phoenix plan tasks with progress tracking. Use after /phx:plan to implement features with mix compile and mix test verification after each step, or --continue to resume interrupted work.