Borrowing it
Nothing to install: this file belongs to CAPHTECH/pce-memory. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CAPHTECH/pce-memory/main/.claude/skills/pce-memory-project-manager/SKILL.mdgit clone --depth 1 https://github.com/CAPHTECH/pce-memoryWrote 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/caphtech/pce-memory/pce-memory-project-manager)<a href="https://agentmods.dev/skills/caphtech/pce-memory/pce-memory-project-manager"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-memory-project-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/caphtech/pce-memory/pce-memory-project-manager"><img src="https://agentmods.dev/badge/skills/caphtech/pce-memory/pce-memory-project-manager.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.00021 | $0.00454 |
| Opus 5.5 | $0.00008 | $0.00182 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
pce-memory-project-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 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.
What it actually says
pce-memory Project Manager
Manage CAPHTECH/pce-memory issue planning through repo-owned automation.
Use This Skill For
- creating or updating milestones for Project #18
- assigning issues to the configured milestone waves
- syncing Project #18 fields from repo config
- verifying drift between GitHub and repo policy
- checking which operational project views are available
Source Of Truth
- Config:
docs/project-management/project-18-config.yaml - Policy:
docs/project-management/project-18-policy.md - Apply script:
scripts/project/apply_project_18.sh - Verify script:
scripts/project/verify_project_18.sh
Read the policy first if the request changes milestone grouping or field conventions.
Workflow
- Inspect the current state with:
scripts/project/verify_project_18.sh - If the request changes the intended state, update:
docs/project-management/project-18-config.yaml - Apply the configured GitHub state with:
scripts/project/apply_project_18.sh - Re-run verification.
- If views are missing or drifted, use the policy doc to reconcile against the existing GitHub default views and then verify again.
Important Rules
- Treat the repo config as the canonical plan, not the current GitHub state.
- Do not hand-edit individual issue fields first and backfill config later.
- Use the apply script for milestone and field updates to keep history reproducible.
- Keep deferred items in deferred milestones unless the config changes.
View Boundary
GitHub public APIs do not currently offer a complete Project V2 view-management surface. This skill therefore treats the existing GitHub views as canonical and verifies these operational views:
Team itemsBacklogRoadmap
Install
Use scripts/project/install_skill.sh to symlink this repo-owned skill into ~/.codex/skills.
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 · 57 lines · 21 tokens per session scan A eba4edbead8a
pce-memory-project-manager is a skill published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 454 once invoked, about $0.0001 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.