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 agentmods add skills/zebbern/pocmap/claude-code-projectnpx skills add zebbern/pocmap --skill claude-code-projectgit clone --depth 1 https://github.com/zebbern/pocmapWhat 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 | $0.00100 | $0.02980 |
| Opus 5 | $0.00050 | $0.01490 |
| Sonnet 5 | $0.00020 | $0.00596 |
| Haiku 4.5 | $0.00010 | $0.00298 |
Grade A, and why
claude-code-project 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 2d 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Project Manager
Manage and maintain Claude Code project configuration files. This skill provides three invokable workflows for keeping your Claude Code setup optimized and in sync with your project.
When to Use Each Command
| Command | Use When |
|---|---|
/update-project |
Project changed (new stack, tools, conventions). User is unsure if CLAUDE.md/AGENTS.md need updates. |
/verify-project |
Want to validate entire .claude setup is correct and functional. Before major changes or periodically. |
/check |
Want to discover what could be improved. Looking for missing tools, MCPs, skills, or config gaps. |
Prerequisites
Before running any command, understand the current project state:
- Check if
.claude/directory orCLAUDE.mdexists in the project root - Check if
AGENTS.mdexists (may be imported by CLAUDE.md) - Identify the project stack (language, framework, build tools) by examining:
package.json,Cargo.toml,pyproject.toml,go.mod, etc.Dockerfile,docker-compose.yml,Makefile,justfile- CI/CD configs (
.github/workflows/,.gitlab-ci.yml) - Test runner configs (
vitest.config.*,jest.config.*,pytest.ini)
- Run
ls -la .claude/or check for.claude/directory structure
/update-project: Update CLAUDE.md and AGENTS.md
Review the current project state and update documentation to reflect reality.
Workflow
- Read existing files: Read current
CLAUDE.md,AGENTS.md, and.claude/contents - Analyze project: Detect the actual stack, tools, commands, and conventions currently in use
- Identify gaps: Compare actual state vs documented state using the checklist in
references/update-project-checklist.md - Update CLAUDE.md: Rewrite or patch to reflect current reality. Follow the template in
assets/claude-md-template.md - Update AGENTS.md: If used, ensure it imports correctly and covers agent conventions
- Summarize changes: Report what changed and why
What ships with it
6 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.
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.
- 2d ago First seen · 315 lines · 100 tokens per session scan A c13de14f3498
claude-code-project is a skill published in the GitHub repository zebbern/pocmap (5 stars, last pushed 9d ago), licensed MIT. It adds 100 tokens to every session and 2,980 once invoked, about $0.0005 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
baoyu-imagine
AI image generation with OpenAI GPT Image 2, Azure OpenAI, Google, OpenRouter, DashScope, Z.AI GLM-Image, MiniMax, Jimeng, Seedream and Replicate APIs. Supports text-to-image, reference images, aspect ratios, and batch generation from saved prompt files. Sequential by default; use batch parallel generation when the…
discernment-nudge
After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE…
observal
Operates the Observal CLI for authentication, configuration, setup diagnosis, teamspaces, inbox work, scans, update checks, and authenticated API access. Use when the user wants to log in, configure Observal, inspect local harness setup, manage a teamspace or invitation, process inbox items, check installed registry…
observal-admin
Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, local server services, upgrades, rollback, and database migrations. Use when the user needs privileged governance, submission decisions, identity configuration, security investigation, or server operations.
observal-advanced
Recovers Observal session ingestion, manages CLI upgrades, downgrades and rollback, and performs explicit local Agent fallback when the server is unavailable. Use when the user asks to reconcile missed sessions, repair CLI version state, or continue locally after a confirmed connection or configuration failure.
observal-agents
Creates, authors, validates, publishes, updates, versions, pulls, archives, restores, transfers, and manages co-authors for Observal Agents. Use when the user wants to build or install an Agent, change an Agent definition, publish a draft, release a version, or manage Agent ownership.