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 ur-grue/autopunk-media-skills --skill foi-data-requestgit clone --depth 1 https://github.com/ur-grue/autopunk-media-skillsWrote 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/ur-grue/autopunk-media-skills/foi-data-request)<a href="https://agentmods.dev/skills/ur-grue/autopunk-media-skills/foi-data-request"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/foi-data-request/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/ur-grue/autopunk-media-skills/foi-data-request"><img src="https://agentmods.dev/badge/skills/ur-grue/autopunk-media-skills/foi-data-request.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Excessive Agency · line 70 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00042 | $0.01444 |
| Opus 5 | $0.00021 | $0.00722 |
| Sonnet 5 | $0.00008 | $0.00289 |
| Haiku 4.5 | $0.00004 | $0.00144 |
Grade A, and why
foi-data-request 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FOI Data Request
What This Skill Does
Drafts a Freedom of Information request specifically targeting datasets, databases, or digital records — written to maximise the chance of receiving complete, machine-readable data rather than summary PDFs or partial tables.
When To Use This Skill
- You want to obtain a specific dataset held by a public body and need the request worded precisely enough to prevent a narrow interpretation
- You have already received an FOI response containing a summary table and want to re-request the underlying data in full
- You want to include specific clauses requesting machine-readable format, codebooks, and data dictionaries alongside the data
- You need to ask for multiple related datasets in a single, clearly organised request
What You Need To Provide
Required: The name of the public body you are submitting to. A description of the data you believe they hold — what it records, the approximate time period, and what you have found in published reports or previous FOIs that suggests it exists. Your name (or a publication name if submitting formally). Optional: Specific columns or fields you know exist; the file format you want the data in (CSV, Excel, database export); any known previous FOI that touched the same data; jurisdiction (to ensure correct statutory references are used).
How the Assistant Approaches This
- Structures the request around the specific data sought — naming fields, date ranges, and systems where known — rather than using vague language that invites partial disclosure.
- Includes standard data-journalist clauses: requesting machine-readable format, a data dictionary or codebook if one exists, and any published schema or data model.
- Adds standard scaffolding: statutory basis for the request, a deadline note, a request for notification if the request is likely to be refused in part, and contact information.
Output Format
A formal letter in three sections: (1) Purpose and identification — who you are and why you are making the request (brief, neutral, no obligation to explain). (2) The request — specific numbered items, each naming the data sought with as much precision as possible. (3) Format and process — your preferred format, a request for the data dictionary, and a note on partial disclosure. Approximately 350–600 words. Formal register throughout.
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.
- 11d ago First seen · 104 lines · 42 tokens per session scan A 31cf281043e3
foi-data-request is a skill published in the GitHub repository ur-grue/autopunk-media-skills (30 stars, last pushed 10d ago), licensed MIT. It adds 42 tokens to every session and 1,444 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
redact-output
This skill should be used when the user asks to "redact PII before publishing", "redact third-party names to initials in a findings note", "redact a note before it goes in the vault", "mask suspect / person-of-interest / minor names that landed in the reason fields", "keep the full un-redacted exhibit local / out of…
archive-evidence
Use when a user receives a FOIA artifact (a released record, a document dump, an export) and wants to record its provenance and establish a chain of custody before any processing. This skill hashes the file on receipt, obtains an RFC 3161 trusted timestamp proving that hash existed at a time, writes an append-only…
foia-requests
FOIA and public records workflows. Use when drafting requests, tracking submissions, checking exemptions, or appealing denials.
content-access
Legal methods for paywalled and geo-blocked content. Use for paywalls, academic papers, or open access via Unpaywall.
web-archiving
Web archiving and retrieval via Wayback Machine and Archive.today. Use to preserve content, reach dead pages, or save evidence.
brazil-records-requests
Public records requests under Brazil's Access to Information Law (LAI). Use for Fala.BR filings, e-SIC, and CGU/CMRI appeals.