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 shunsock/dotfiles --skill prepare__issuegit clone --depth 1 https://github.com/shunsock/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/shunsock/dotfiles/prepare__issue)<a href="https://agentmods.dev/skills/shunsock/dotfiles/prepare__issue"><img src="https://agentmods.dev/badge/skills/shunsock/dotfiles/prepare__issue/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/shunsock/dotfiles/prepare__issue"><img src="https://agentmods.dev/badge/skills/shunsock/dotfiles/prepare__issue.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.00145 | $0.02687 |
| Opus 5.5 | $0.00058 | $0.01075 |
| Sonnet 5.5 | $0.00029 | $0.00537 |
| Haiku 4.5 | $0.00015 | $0.00269 |
Grade A, and why
prepare__issue 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 173 lines · 145 tokens per session scan A 53d198ff8d3d
prepare__issue is a skill published in the GitHub repository shunsock/dotfiles (10 stars, last pushed 26d ago), with no licence file. It adds 145 tokens to every session and 2,687 once invoked, about $0.0006 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
show-issues-overview
Show a table-formatted overview of the current repository's issues, from GitHub Issues, GitLab Issues, or a TODO.md-like file when the project has neither. Use when the user asks what issues/tasks are open, wants to decide what to work on next, or invokes /show-issues-overview.
sync-labels-from-prs-and-sub-issues
A workflow for calculating area labels from the files changed by pull requests and sub-issues, then synchronizing those labels across related GitHub items. Labels are tags used to group and filter work.
link-this-pr-to-issue
A GitHub procedure for linking a pull request (PR) to an issue, a GitHub task or bug report, by adding a closing phrase such as “Closes #123” to the PR description. Merging the PR can then close the linked issue automatically.
sync-issue-title-and-detail-to-this-pr
A workflow for keeping a pull request's title and summary aligned with its parent GitHub issue. A pull request is a proposed code change, while an issue tracks the work or problem behind it.
create-this-issue
A GitHub issue-creation workflow that turns the current task into a tracked issue. A GitHub issue is a shared record of work, including its purpose, requirements, and completion conditions.
coding
Principles for writing, changing, and testing code, covering readability at every scale, abstraction and naming, interfaces, comments and documentation, tests as maintained code, and standards of evidence for claims about code behavior.