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 zebbern/pocmap --skill claude-code-projectgit clone --depth 1 https://github.com/zebbern/pocmapWrote 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/zebbern/pocmap/claude-code-project)<a href="https://agentmods.dev/skills/zebbern/pocmap/claude-code-project"><img src="https://agentmods.dev/badge/skills/zebbern/pocmap/claude-code-project/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/zebbern/pocmap/claude-code-project"><img src="https://agentmods.dev/badge/skills/zebbern/pocmap/claude-code-project.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.00100 | $0.02980 |
| Opus 5.5 | $0.00040 | $0.01192 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (6 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 2,980 once invoked, about $0.0004 per session on Opus 5.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
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
observal-agents
Creates, forks, 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.
observal-registry
Searches, recommends, bulk-submits, installs, forks, edits, versions, archives, restores, transfers, and manages co-authors for Observal MCP servers, skills, hooks, prompts, sandboxes, and registered remote A2A agents. Use when the user wants to find components, publish one or many they control, install them into a…
observal-admin
Administers Observal users, settings, diagnostics, review queues, security events, audit logs, SAML, SCIM, the local Observal server, its upgrades and rollback, and its own PostgreSQL and ClickHouse schema migrations. Use when the user needs privileged governance, submission decisions, identity configuration, security…
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-ops
Inspects Observal traces, sessions, rankings, feedback, telemetry health, logs, and Agent insight reports. Use when the user wants operational evidence, current activity, telemetry diagnosis, ratings, report generation, regression analysis, or recommendations grounded in Agent usage.