Borrowing it
Nothing to install: this file belongs to impierce/ssi-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/impierce/ssi-agent/beta/.agents/skills/setup-matt-pocock-skills/SKILL.mdgit clone --depth 1 https://github.com/impierce/ssi-agentWrote 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/impierce/ssi-agent/setup-matt-pocock-skills)<a href="https://agentmods.dev/skills/impierce/ssi-agent/setup-matt-pocock-skills"><img src="https://agentmods.dev/badge/skills/impierce/ssi-agent/setup-matt-pocock-skills/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/impierce/ssi-agent/setup-matt-pocock-skills"><img src="https://agentmods.dev/badge/skills/impierce/ssi-agent/setup-matt-pocock-skills.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.00124 | $0.01703 |
| Opus 5.5 | $0.00050 | $0.00681 |
| Sonnet 5.5 | $0.00025 | $0.00341 |
| Haiku 4.5 | $0.00012 | $0.00170 |
Grade A, and why
setup-matt-pocock-skills 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 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.
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.
This is a copy
97% identical to setup-matt-pocock-skills — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Matt Pocock's Skills
Scaffold the per-repo configuration that the engineering skills assume:
- Issue tracker — where issues live (GitHub by default; local markdown is also supported out of the box)
- Triage labels — the strings used for the five canonical triage roles
- Domain docs — where
CONTEXT.mdand ADRs live, and the consumer rules for reading them
This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
Process
1. Explore
Look at the current repo to understand its starting state. Read whatever exists; don't assume:
git remote -vand.git/config— is this a GitHub repo? Which one?AGENTS.mdandCLAUDE.mdat the repo root — does either exist? Is there already an## Agent skillssection in either?CONTEXT.mdandCONTEXT-MAP.mdat the repo rootdocs/adr/and anysrc/*/docs/adr/directoriesdocs/agents/— does this skill's prior output already exist?.scratch/— sign that a local-markdown issue tracker convention is already in use
2. Present findings and ask
Summarise what's present and what's missing. Then walk the user through the three decisions one at a time — present a section, get the user's answer, then move to the next. Don't dump all three at once.
Assume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.
Section A — Issue tracker.
Explainer: The "issue tracker" is where issues live for this repo. Skills like
to-issues,triage,to-prd, andqaread from and write to it — they need to know whether to callgh issue create, write a markdown file under.scratch/, or follow some other workflow you describe. Pick the place you actually track work for this repo.
Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:
What ships with it
5 files 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.
- 2d ago First seen · 122 lines · 124 tokens per session scan A c778d4e3d86e
setup-matt-pocock-skills is a skill published in the GitHub repository impierce/ssi-agent (21 stars, last pushed 3d ago), licensed Apache-2.0. It adds 124 tokens to every session and 1,703 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 97% identical to setup-matt-pocock-skills, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
e-signature
Use when wiring an e-signature flow with DocuSign or Dropbox Sign — picking the SES/AES/QES legal tier, sending a PDF or template for signature, embedded signing, verifying signing webhooks, retrieving the signed PDF plus audit trail. NOT drafting contract text (that is contracts), NOT extracting fields from PDFs…
datenschutz-folgenabschaetzung-pruefung
Pruefung ob fuer ein Verfahren eine Datenschutz-Folgenabschaetzung nach Art. 35 DSGVO erforderlich ist und welche Schritte sie umfasst. Methodik Pruefung der Risikoindikatoren fuer ein hohes Risiko Abgleich mit Positivlisten der Aufsichtsbehoerden Pruefung des Ablaufs einer Folgenabschaetzung samt Risikobewertung und…
digitales-bildungswesen-schulverwaltung-pruefung
Prueft den Digitalisierungsstand von Schulverwaltungsprozessen eines Schultraegers bzw. einer Kommune zum Beispiel Schulanmeldung Lernplattform-Anbindung und Schulverwaltungssoftware. Methodik Sachverhaltsaufbereitung Einordnung Anforderungen Umsetzungsschritte Ergebnis. Output ausformulierte Pruefung mit Ergebnis zum…
datengetriebene-entscheidung-open-data-pruefung
Pruefung der Voraussetzungen fuer datengetriebene Entscheidungen einer Behoerde oder die Bereitstellung von Verwaltungsdaten als Open Data. Methodik Pruefung der Rechtsgrundlage Pruefung der Datenqualitaet und Data Governance Pruefung von Anonymisierung und Re-Identifikationsrisiko Einordnung nach den Open-Data- und…
eudi-wallet-einsatzpruefung
Pruefung ob und wie eine digitale Wallet zum Beispiel die EUDI-Wallet zur Vorlage von Nachweisen oder Attributen fuer eine Verwaltungsleistung genutzt werden kann. Methodik Analyse der benoetigten Nachweise Pruefung der Ausstellung als Attestierung Pruefung des Empfangs und der Verifikation durch die Behoerde…
it-sicherheit-grundschutz-checkliste
Checkliste der grundlegenden BSI-IT-Grundschutz-Anforderungen bei Einfuehrung eines neuen digitalen Verfahrens in einer Behoerde. Methodik Strukturanalyse und Schutzbedarfsfeststellung Abgleich mit einschlaegigen Bausteinen des IT-Grundschutz-Kompendiums Pruefung von Basisanforderungen zu Organisation Technik und…