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 agentmods add skills/jlong/quiddity/q-setup-approvenpx skills add jlong/quiddity --skill q-setup-approvegit clone --depth 1 https://github.com/jlong/quiddityWrote 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/jlong/quiddity/q-setup-approve)<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-approve"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-approve.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.00050 | $0.00597 |
| Opus 5 | $0.00025 | $0.00298 |
| Sonnet 5 | $0.00010 | $0.00119 |
| Haiku 4.5 | $0.00005 | $0.00060 |
Grade A, and why
q-setup-approve 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup /approve
You are generating a custom /approve skill for the user's project.
Required categories
This skill needs the following tools.json categories: source-control, ci, pr
Process
-
Ensure tools are configured. Check if
.quiddity/tools.jsonexists and contains thesource-control,ci, andprcategories. For any missing categories, run/q-which-toolswith those categories (e.g.,/q-which-tools source-control ci pr). -
Read the configuration. Load all available Quiddity context:
.quiddity/project.md— project structure, CI/CD configuration.quiddity/process.md— merge strategy, review requirements, post-merge workflow.quiddity/tools.json— extract thesource-control,ci, andprcategories
-
Ask skill-specific questions not covered by tools.json:
- Should the skill accept a PR number as an argument? (e.g.,
/approve 123) Or default to the current branch's PR? - What should happen after merge? (update issue status, notify, etc.)
- Should it verify that all review comments are resolved?
- Any post-merge cleanup steps? (delete local branch, pull latest, etc.)
- Should the skill accept a PR number as an argument? (e.g.,
-
Generate the skill. Write a complete
/approveSKILL.md to the project's skills directory. The generated skill should:- Accept an optional PR number argument (defaulting to current branch's PR)
- Verify all CI checks pass
- Verify no unresolved review comments (if configured)
- Verify required approvals are met
- Perform the merge using the configured strategy (squash, merge, rebase)
- Update the linked issue status (e.g., move to "Done" or "Shipped")
- Clean up the branch if configured
- Report clearly if anything blocks the merge
- Reference
.quiddity/tools.jsonfor all tool-specific configuration
-
Show the generated skill to the user and ask for confirmation before finalizing.
Generated skill template
The generated /approve skill should follow this general structure, adapted
to the user's specific tools:
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 · 68 lines · 50 tokens per session scan A 4ccd9681ff70
q-setup-approve is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 597 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…