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 SienkLogic/plan-build-run --skill profile-usergit clone --depth 1 https://github.com/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/profile-user)<a href="https://agentmods.dev/skills/sienklogic/plan-build-run/profile-user"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/profile-user/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/sienklogic/plan-build-run/profile-user"><img src="https://agentmods.dev/badge/skills/sienklogic/plan-build-run/profile-user.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.00019 | $0.02012 |
| Opus 5.5 | $0.00008 | $0.00805 |
| Sonnet 5.5 | $0.00004 | $0.00402 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade B, and why
profile-user scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
find ~/.claude/projects/{encoded-path}/ -name "*.jsonl" -size +1k 2>/dev/null | wc -l How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's plugin system. Using the Read tool on this SKILL.md file wastes tokens. Begin executing Step 0 immediately.
Step 0 -- Banner
Before ANY tool calls, display this banner:
╔══════════════════════════════════════════════════════════════╗
║ PLAN-BUILD-RUN ► USER PROFILE ║
╚══════════════════════════════════════════════════════════════╝
Then proceed to Step 1.
/pbr:profile-user -- Developer Behavioral Profiling
You are running the profile-user skill. Your job is to analyze the user's Claude Code session history across 8 behavioral dimensions and generate a .planning/USER-PROFILE.md file with actionable insights. If insufficient session data exists, fall back to a short interactive questionnaire.
Step 1 -- Config Gate
Check if the developer profiling feature is enabled:
pbr-tools config get developer_profile.enabled
- If the result is
false, empty, or the key is missing: tell the user to enable it first with/pbr:config set developer_profile.enabled trueand STOP. - If
true: proceed to Step 2.
Step 2 -- Locate Session Logs
Find the Claude Code session log directory for this project:
# List ~/.claude/projects/ to find the encoded project path
ls -la ~/.claude/projects/
The directory name is the project root path with path separators replaced by -. For example, D:\Repos\plan-build-run becomes something like D--Repos-plan-build-run or D-Repos-plan-build-run.
Once found, list JSONL files sorted by modification time:
ls -lt ~/.claude/projects/{encoded-path}/*.jsonl 2>/dev/null | head -20
Count the files that are larger than 1KB:
find ~/.claude/projects/{encoded-path}/ -name "*.jsonl" -size +1k 2>/dev/null | wc -l
Step 3 -- Analysis or Fallback Decision
- If >= 3 session JSONL files found (each > 1KB): proceed to Step 4 (session analysis mode).
- If < 3 usable session files: proceed to Step 5 (questionnaire fallback).
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 · 228 lines · 19 tokens per session scan B de031d5f26e5
profile-user is a skill published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 2,012 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
self-assessment
Interactive skill assessment with personalized learning path generation.
investigate
Systematic root-cause debugging: find the cause before writing any fix.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eight checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
talk-stage3-concepts
Builds a numbered, categorized concept catalogue from the talk summary and timeline, scoring each concept HIGH / MEDIUM / LOW for talk potential with optional repo enrichment. Use when you need a structured inventory of concepts before choosing a talk angle, or when assessing which ideas have the strongest…
talk-stage4-position
Generates 3-4 strategic talk angles with strength/weakness analysis, title options, CFP descriptions, and a peer feedback draft, then enforces a mandatory CHECKPOINT for user confirmation before scripting. Use when deciding how to frame a talk, preparing a CFP submission, or choosing between multiple narrative angles.