Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/instructions/afcondon/purescript-agent-skills/claude-md)<a href="https://agentmods.dev/instructions/afcondon/purescript-agent-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/afcondon/purescript-agent-skills/claude-md.svg" alt="Measured on agentmods" 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.01029 | $0.01029 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
purescript-agent-skills CLAUDE.md 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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PureScript Ecosystem Guide
Goal
Create a concise, AI-to-AI reference of the PureScript package ecosystem. The primary audience is Claude (or other AI assistants) helping developers write PureScript. The guide should provide the practical knowledge that's missing from training data — which packages to reach for, cultural conventions, and "don't do this, do that" guidance.
Why This Exists
PureScript is a niche language. Claude's PureScript knowledge is largely inferred from Haskell training data, which leads to:
- Suggesting Haskell idioms that don't apply (e.g., type class instances for JSON instead of codec values)
- Not knowing about key packages (e.g.,
codec-argonaut,halogen,httpure) - Missing ecosystem conventions (e.g.,
Afffor async,Effectfor sync, neverIO) - Not understanding the package split patterns (e.g.,
affjaxvsaffjax-webvsaffjax-node)
Data Sources
Package set (current versions)
/Users/afc/work/afc-work/CodeExplorer/minard/database/_registry-index/package-set-71.0.0.json
- 568 packages with current version numbers
- Quick lookup for what's available
Registry index (all versions, with manifests)
/Users/afc/work/afc-work/registry-index/
- 2-char prefix directory structure (e.g.,
af/fj/affjax) - Each file contains JSONL: one JSON object per published version
- Includes: name, version, license, description, location (GitHub), dependencies
- 1282 total manifest files
Package source code
For deeper review, fetch from GitHub using the location info in manifests.
Use gh api or clone repos as needed.
Output Format
Per-package review (for important packages)
## package-name
**What:** One-sentence description
**When to use:** The trigger condition — when should an AI suggest this?
**Key exports:** 3-5 most important types/functions
**Instead of:** What NOT to do (the common mistake this prevents)
**Ecosystem role:** core | contrib | community | niche
**Status:** active | maintained | dormant | deprecated
**Note:** Any PureScript-specific convention that differs from Haskell
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.
- 5d ago First seen · 93 lines · 1,029 tokens per session scan A 41f3b1d85cff
purescript-agent-skills CLAUDE.md is an instructions file published in the GitHub repository afcondon/purescript-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,029 tokens to every session, about $0.0051 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-31.
Other instructions, from other repositories
dingtalk-workspace-cli AGENTS.md
AGENTS.md instructions for DingTalk-Real-AI/dingtalk-workspace-cli, covering repository agent guide, build and test, command framework declaration, flag / help / schema homology and agent schema contract.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
vespertide AGENTS.md
AGENTS.md instructions for dev-five-git/vespertide, covering vespertide knowledge base, structure, where to look, data flow and conventions.
unity-code-style-guide AGENTS.md
Instructions for krogh-jacobsen/unity-code-style-guide, covering agents.md — unity 6 c, project setup — edit this block, never do these — they corrupt the project, deprecated in unity 6 and if you read nothing else.
rubydex AGENTS.md
AGENTS.md instructions for Shopify/rubydex, covering instructions, project overview, documentation, ruby gem and structure.