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 commands/fcakyon/phd-skills/setupgit clone --depth 1 https://github.com/fcakyon/phd-skillsWhat 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.00030 | $0.01516 |
| Opus 5 | $0.00015 | $0.00758 |
| Sonnet 5 | $0.00006 | $0.00303 |
| Haiku 4.5 | $0.00003 | $0.00152 |
Grade C, and why
setup scanned grade C with 3 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
- **ntfy.sh**: ask for topic name, write to `.env` as `NTFY_TOPIC=<topic>`. Test with `curl -d "phd-skills test" ntfy.sh/<topic>` Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **Suppress a hook**: edit `~/.claude/settings.json` and set `"hooks.<event>.<matcher>.disabled": true` (Claude Code's standard mechanism) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **ntfy.sh**: ask for topic name, write to `.env` as `NTFY_TOPIC=<topic>`. Test with `curl -d "phd-skills test" ntfy.sh/<topic>` How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHD-Skills Setup
The plugin works correctly the moment it is installed. Most users never need to run setup. This command exists to (1) show what was auto-detected on the user's system, and (2) let users opt into a few extras (notifications, allowlist, project CLAUDE.md, LaTeX).
Step 0: Auto-detection tour (always run first)
Before asking any questions, print what the plugin already knows. No prompts, no decisions, just visibility.
Run these probes silently and present the results:
# System timezone
sys_tz=$(date +%Z)
sys_tz_long=$(readlink /etc/localtime 2> /dev/null | sed 's|.*zoneinfo/||')
# Last few long-job launches the plugin would have flagged
recent_launches=$(history 200 2> /dev/null | grep -E '(python.*train|accelerate launch|torchrun|deepspeed|sbatch|tmux.*python)' | tail -5)
# Sample jargon-shape hits in user's recent commits (if in a git repo)
jargon_hits=$(git log -50 --pretty=format:%s 2> /dev/null | grep -E '\bwave-[0-9]+\b|\bphase-internal\b|\binternal-only\b' | head -3)
# What the agentic Stop hook would orient on for this project
project_orientation=""
[ -f README.md ] && project_orientation+="README.md found "
[ -f CLAUDE.md ] && project_orientation+="CLAUDE.md found "
[ -f .claude/CLAUDE.md ] && project_orientation+=".claude/CLAUDE.md found "
[ -f AGENTS.md ] && project_orientation+="AGENTS.md found "
Then present:
phd-skills auto-detected the following:
Timezone: ${sys_tz} (${sys_tz_long})
Recent launches: <count> training-job patterns in shell history
Jargon hits: <count> commits with internal-jargon shapes
Project orientation: ${project_orientation:-no README / CLAUDE.md / AGENTS.md found at project root}
This is what the hooks and agentic Stop hook will use. No configuration needed.
The plugin works on the first command. Hooks fire silently when there is nothing to flag.
Want to configure any extras? (notifications, allowlist, CLAUDE.md, LaTeX) [y/N]
If the user says no, you are done. If yes, walk them through the optional steps below.
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 · 165 lines · 30 tokens per session scan C 2d959f74b135
setup is a command published in the GitHub repository fcakyon/phd-skills (377 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 1,516 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 3 findings (sends data to an external url, reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
design-review
Workflow recipe — review a design end-to-end, ending in measured numbers rather than adjectives, by chaining 4 skills.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
security-review
CWE 기반 보안 검토 + STRIDE 위협 모델링 (v6 - effort:max 강제).
release-harn
Run the tag-first Harn release workflow.
discover
Search the Everruns(Dev) API catalog for available operations.