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/fredrikaverpil/dotfiles/plan-interviewnpx skills add fredrikaverpil/dotfiles --skill plan-interviewgit clone --depth 1 https://github.com/fredrikaverpil/dotfilesWrote 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/fredrikaverpil/dotfiles/plan-interview)<a href="https://agentmods.dev/skills/fredrikaverpil/dotfiles/plan-interview"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/plan-interview.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.00000 | $0.00014 |
| Opus 5 | $0.00000 | $0.00007 |
| Sonnet 5 | $0.00000 | $0.00003 |
| Haiku 4.5 | $0.00000 | $0.00001 |
Grade A, and why
plan-interview 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
../../../.claude/skills/plan-interview/SKILL.md
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 · 1 lines · 0 tokens per session scan A 19985c62b7d8
plan-interview is a skill published in the GitHub repository fredrikaverpil/dotfiles (256 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 14 tokens. 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-30.
Other skills, from other repositories
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
pr-list
List GitHub Pull Requests in a Discord-friendly format with status icons, blockquotes, and direct links. Use when the user asks for "pr list", "list PRs", "open pull requests", or a chat-ready summary of PRs for a repository.
google-docs
Integration for interacting with Google Docs and Google Workspace using the 'gws' CLI.
sync-forks
Check how many of your GitHub forks are out of date and sync them.
research-evaluation
Discover and evaluate external tools/projects before adopting them, producing a consistent research dossier and (when the repo has one) a docs/mbo research design doc + tracking issue per target. Use when the user wants to "research X", "evaluate X before we adopt it", "look up X and tell me if it's useful", "start a…