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 shmindmaster/gitpin --skill gitpingit clone --depth 1 https://github.com/shmindmaster/gitpinWrote 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/shmindmaster/gitpin/gitpin)<a href="https://agentmods.dev/skills/shmindmaster/gitpin/gitpin"><img src="https://agentmods.dev/badge/skills/shmindmaster/gitpin/gitpin/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/shmindmaster/gitpin/gitpin"><img src="https://agentmods.dev/badge/skills/shmindmaster/gitpin/gitpin.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.00061 | $0.00365 |
| Opus 5.5 | $0.00024 | $0.00146 |
| Sonnet 5.5 | $0.00012 | $0.00073 |
| Haiku 4.5 | $0.00006 | $0.00036 |
Grade A, and why
gitpin 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.
What it actually says
GitPin skill
Product contract
- Index-free, read-only, Git HEAD only
- Dirty / untracked files are not evidence
- Job: prove and verify claims with path + line + full SHA
Required loop
pin.catalog— discover registry roots and HEAD SHAspin.search_docs/pin.search_code— candidates onlypin.prove(one path) orpin.prove_set(1–8 multi-cite)pin.verifyorpin.verify_set— close the loop- Multi-repo decisions →
pin.analyzewithoperation: "brief"
Citation rules
- Copy
citation.citeorcitation.handleexactly into answers - Prefer
mustContainon verify when asserting a quote or keyword - If status is
missing,blocked, orcontradicted, say so — do not invent content
CLI (same contract)
gitpin doctor
gitpin verify --repository <n> --path <p> --sha <hex> [--line <n>] [--must-contain <text>]
gitpin verify --from-pack pack.json
gitpin verify-cites --file notes.md
See docs/cite-spec.md and docs/tools.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.
- 1mo ago First seen · 41 lines · 61 tokens per session scan A 3363415a5d7d
gitpin is a skill published in the GitHub repository shmindmaster/gitpin (0 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 365 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
triage-contributor-pr
Triage open pull requests from external contributors to prisma/orm and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
review-triage-phase
Produces canonical review actions from fetched review state and renders action markdown. Use when the user wants only triage/action-planning for the review-framework workflow.
update-pr
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
writing-emdash-docs
Write, revise, and review EmDash documentation for technical accuracy, useful structure, house style, and natural prose. Use when working on user documentation, guides, API reference pages, migration or upgrade guides, READMEs, contributor documentation, technical specifications, or release notes in the EmDash…
agent-debug-ci
Investigate failed scheduled or nightly GitHub Actions runs on the default branch, determine whether the failure is reproducible and repository-owned, implement the smallest evidence-backed fix, validate it, and open a pull request. Use when a failed nightly CI event starts an agent, or when the standard CI or…