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 MisterClean/claude-plugins --skill cook-county-data-portalgit clone --depth 1 https://github.com/MisterClean/claude-pluginsWrote 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/misterclean/claude-plugins/cook-county-data-portal)<a href="https://agentmods.dev/skills/misterclean/claude-plugins/cook-county-data-portal"><img src="https://agentmods.dev/badge/skills/misterclean/claude-plugins/cook-county-data-portal/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/misterclean/claude-plugins/cook-county-data-portal"><img src="https://agentmods.dev/badge/skills/misterclean/claude-plugins/cook-county-data-portal.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.00090 | $0.02277 |
| Opus 5 | $0.00045 | $0.01138 |
| Sonnet 5 | $0.00018 | $0.00455 |
| Haiku 4.5 | $0.00009 | $0.00228 |
Grade A, and why
cook-county-data-portal scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST \ How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cook County Data Portal Skill
Query and download datasets from the Cook County Open Data Portal using the Socrata Open Data API (SODA) and SoQL.
Prerequisites
Before querying, check if the user has an app token:
- Look for
COOK_COUNTY_DATA_PORTAL_TOKENin the user's.envfile - If not found, check for
CHICAGO_DATA_PORTAL_TOKEN(both portals use Socrata, so tokens are interchangeable) - If found, use it in requests via header:
X-App-Token: <token> - If neither token exists, instruct the user to:
- Sign up at https://datacatalog.cookcountyil.gov/signup (or https://data.cityofchicago.org/signup)
- Create an app token in Developer Settings
- Add to
.env:COOK_COUNTY_DATA_PORTAL_TOKEN=your_token_here
Queries work without a token but are rate-limited.
Quick Start
The Cook County Data Portal is at datacatalog.cookcountyil.gov. Each dataset has a unique 4x4 ID (e.g., uzyt-m557 for assessed values). Use the catalog API to discover datasets, then query via SODA.
Workflow
Step 1: Clarify the Data Need
Ask the user:
- Topic: What data? (property assessments, court cases, payroll, medical examiner, etc.)
- Geography: Countywide, township, municipality, or specific parcel/PIN?
- Time window: Date range, tax year, or fiscal quarter?
- Output: JSON (code) or CSV (Excel)?
- Granularity: Raw rows or aggregated counts?
Step 2: Find the Dataset
Option A - Catalog Search API:
GET https://api.us.socrata.com/api/catalog/v1?domains=datacatalog.cookcountyil.gov&q=<keywords>
Option B - Portal UI: Browse https://datacatalog.cookcountyil.gov and use the search bar.
Deliverable: Dataset name, 4x4 ID, and API endpoint.
See references/datasets-*.md for commonly requested datasets by category:
references/datasets-property.md- Assessor, Treasurer, parcel datareferences/datasets-courts.md- State's Attorney, sentencing, dispositionsreferences/datasets-health.md- Medical Examiner casesreferences/datasets-finance.md- Payroll, procurement, budgets
What ships with it
9 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.
- .claude-plugin/plugin.json 187 B
- examples/curl-examples.sh 4.2 KB runs code
- examples/python-query.py 5.3 KB runs code
- README.md 2.0 KB
- references/datasets-courts.md 5.5 KB
- references/datasets-finance.md 8.0 KB
- references/datasets-health.md 5.6 KB
- references/datasets-property.md 6.8 KB
- references/soql-quick-ref.md 4.1 KB
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.
- 10d ago First seen · 245 lines · 90 tokens per session scan A 4e9446e6d41c
cook-county-data-portal is a skill published in the GitHub repository MisterClean/claude-plugins (3 stars, last pushed 7mo ago), licensed MIT. It adds 90 tokens to every session and 2,277 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
dummy-dataset
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.
outcome-roadmap
Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
shipping-artifacts
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded…
competitive-battlecard
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'.