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-which-toolsnpx skills add jlong/quiddity --skill q-which-toolsgit 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-which-tools)<a href="https://agentmods.dev/skills/jlong/quiddity/q-which-tools"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-which-tools.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 | $0.00041 | $0.01225 |
| Opus 5 | $0.00020 | $0.00613 |
| Sonnet 5 | $0.00008 | $0.00245 |
| Haiku 4.5 | $0.00004 | $0.00122 |
Grade A, and why
q-which-tools 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 4d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/q-which-tools
You are interviewing the user about the tools their project uses. Your job is
to ask about each requested category and write the results to
.quiddity/tools.json.
Arguments
$ARGUMENTS contains space-separated category names. Supported categories:
- issues — Issue/task tracker (Linear, GitHub Issues, Jira, etc.)
- source-control — Source control host (GitHub, GitLab, Bitbucket, etc.)
- ci — Continuous integration (GitHub Actions, CircleCI, etc.)
- pr — Pull request conventions (merge strategy, review requirements, etc.)
- deploy — Deployment target (Vercel, AWS, Fly, manual, etc.)
- notifications — Notification channels (Slack, Discord, email, etc.)
If no arguments are provided, ask the user which categories they'd like to configure.
Process
-
Read process context. Check if
.quiddity/process.mdexists. If it does, read it to understand the user's SDLC. Use this context to inform your questions and pre-fill answers where possible (e.g., if the process doc mentions "we use GitHub flow", you already know the source-control platform). -
Read existing config. Check if
.quiddity/tools.jsonexists. If it does, read it and note which categories are already configured. -
For each requested category:
- If the category already exists in tools.json, tell the user it's already configured and show the current value. Ask if they want to reconfigure it. If not, skip it.
- If the category is new, ask the user what tool they use.
- Ask follow-up questions specific to the tool they selected. See the category reference below for what to ask.
-
Write the results. Merge the new category data into
.quiddity/tools.json. Create the.quiddity/directory if it doesn't exist. Preserve any existing categories that weren't reconfigured.
Category reference
issues
Ask:
- Which issue tracker? (Linear, GitHub Issues, Jira, Shortcut, etc.)
- Team or project name?
- What states/statuses do issues move through? (e.g., Todo → In Progress → Done)
- How is priority represented? (priority field, labels, columns, etc.)
- Any label conventions?
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.
- 4d ago First seen · 174 lines · 41 tokens per session scan A 7cfc2e4bc85b
q-which-tools is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 1,225 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…