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/shrekshrek/project-workflow/project-personalizenpx skills add shrekshrek/project-workflow --skill project-personalizegit clone --depth 1 https://github.com/shrekshrek/project-workflowWrote 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/shrekshrek/project-workflow/project-personalize)<a href="https://agentmods.dev/skills/shrekshrek/project-workflow/project-personalize"><img src="https://agentmods.dev/badge/skills/shrekshrek/project-workflow/project-personalize.svg" alt="Measured on agentmods" 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 | $0.00029 | $0.00330 |
| Opus 5 | $0.00015 | $0.00165 |
| Sonnet 5 | $0.00006 | $0.00066 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
project-personalize 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 4d 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
Project Personalize
Match the user's language and preserve file language. Read ${CLAUDE_PLUGIN_ROOT}/docs/actions/project-personalize.md completely before acting; it owns the portable workflow and contract.
Claude execution details:
- Parse
$ARGUMENTSas an optional target, include dotfiles in inspection, exclude version-control metadata from content classification, and apply the canonical target classification and route. - Inspect with Read/Grep/Glob/Bash. Use
codebase-explorer,tech-researcher, anddecision-completeness-auditoronly at their canonical boundaries. - For a partial/missing baseline, use
${CLAUDE_PLUGIN_ROOT}/scripts/materialize-project-baseline.cjs --stagein a disposable directory. - Include
.claude/rules/only within the selected convention scope; preserve unrelated project configuration. - Read
${CLAUDE_PLUGIN_ROOT}/docs/actions/project-personalize-reference.mdonly when repository evidence or a user decision makes a specific section relevant; it supplies examples, never defaults. - Use inline trace or fresh named agents at those canonical boundaries; fallback follows the shared execution contract.
- Preflight and apply staged changes under the current request's authorization. An unsafe destination symlink/conflict or blocking audit leaves the target unchanged.
- Do not rewrite feature history or commit.
Report the canonical compact result and applicable Reviewer execution without adding an adapter-specific schema.
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.
- 4d ago First seen · 25 lines · 29 tokens per session scan A 998c23e98818
project-personalize is a skill published in the GitHub repository shrekshrek/project-workflow (2 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 330 once invoked, about $0.0001 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
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
watch
File sentinel that monitors the working directory for changes and marker comments, then auto-triggers appropriate skills. Poll-based via git diff against the last scan commit. Writes intake items for batch processing and routes marker actions through /do. Use for automatic reactions to file changes; do NOT use for…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
review
5-pass structured code review — correctness, security, performance, readability, consistency.