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 aaronbassett/agent-foundry --skill checklist-generatorgit clone --depth 1 https://github.com/aaronbassett/agent-foundryWrote 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/aaronbassett/agent-foundry/checklist-generator)<a href="https://agentmods.dev/skills/aaronbassett/agent-foundry/checklist-generator"><img src="https://agentmods.dev/badge/skills/aaronbassett/agent-foundry/checklist-generator/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/aaronbassett/agent-foundry/checklist-generator"><img src="https://agentmods.dev/badge/skills/aaronbassett/agent-foundry/checklist-generator.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.00050 | $0.01124 |
| Opus 5 | $0.00025 | $0.00562 |
| Sonnet 5 | $0.00010 | $0.00225 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
constitution:checklist-generator 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 8d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Constitution Checklist Generator
You are generating an Implementation Checklist from a project's CONSTITUTION.md file.
Goal
Distill constitutional principles into 6-12 actionable, verifiable checkbox items that engineers can use to validate their work complies with project governance.
Workflow
1. Locate Constitution
Search for CONSTITUTION.md:
- Current directory
- Parent directories (walk up tree)
- Git root if available
If not found: Error with "No CONSTITUTION.md found. Run constitution:writer first."
2. Extract Principles
Parse CONSTITUTION.md:
- Identify
##sections (principles) - Extract core requirements from each section
- Ignore preamble, changelog, footer
3. Distill to Checkboxes
Target: 6-12 items total (fewer is better)
Guidelines:
- Combine related sub-rules into single checkbox
- Make specific and verifiable (not "Write good code")
- Prioritize NON-NEGOTIABLE items first
- Use active voice ("Ensure X", "Verify Y", "Document Z")
Example Transformations:
-
Principle: "Single Responsibility - Each function does one thing" → Checkbox:
[ ] Functions have single, clear purpose (check for multi-responsibility) -
Principle: "No Silent Failures - Always log errors, never empty catch" → Checkbox:
[ ] Error handlers log context (no empty catch/except blocks) -
Principle: "Test Coverage - 80% minimum, integration tests for APIs" → Checkbox:
[ ] Test coverage ≥80% with integration tests for all API endpoints
4. Semantic Deduplication (If Existing Checklist)
When ## Implementation Checklist section exists:
Algorithm:
- Parse existing checklist items (strip
[ ]prefixes) - Parse newly generated items
- For each existing item:
- Find semantic match in new items (keyword similarity)
- If match found: KEEP existing wording (preserve customization)
- If no match: REMOVE (outdated principle)
- For each new item:
- If not covered by kept items: ADD
- If similar to kept item: Compare specificity
- Keep more specific version
- Log decision: "Kept existing item (more specific)"
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.
- 8d ago First seen · 163 lines · 50 tokens per session scan A 9569ef453db6
constitution:checklist-generator is a skill published in the GitHub repository aaronbassett/agent-foundry (4 stars, last pushed 23d ago), licensed MIT. It adds 50 tokens to every session and 1,124 once invoked, about $0.0003 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…