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-processnpx skills add jlong/quiddity --skill q-which-processgit clone --depth 1 https://github.com/jlong/quiddityWhat 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.00931 |
| Opus 5 | $0.00020 | $0.00465 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
q-which-process 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/q-which-process
You are discovering the user's software development lifecycle (SDLC). Your job
is to understand how they work — not what tools they use (that's /q-which-tools),
but the workflow, conventions, and processes that govern their development cycle.
Process
-
Read project context. Check if
.quiddity/project.mdexists. If it does, read it to understand the project structure, tech stack, and any conventions already documented. Use this to inform your questions. -
Check for existing documentation. Ask the user:
- "Do you have a document that describes your development process? You can share a file path, URL, or paste the contents."
- If they provide a document, read it and extract the relevant details below.
- If not, interview them using the questions below.
-
Check for existing process.md. If
.quiddity/process.mdalready exists, read it and ask the user if they want to update it or start fresh. -
Interview the user about the following areas (skip any that were covered by a shared document):
Branching strategy
- What branching model? (trunk-based, git-flow, GitHub flow, etc.)
- Base/main branch name?
- Branch naming conventions? (e.g.,
feat/,fix/,chore/prefixes) - Do feature branches live long or are they short-lived?
- Any release branches?
Code review process
- Are PRs required for all changes?
- How many reviewers are required?
- Who typically reviews? (team lead, any team member, CODEOWNERS, etc.)
- Any review conventions? (e.g., "approve with comments" vs "request changes")
- Turnaround time expectations?
Issue workflow
- How does work get prioritized and assigned?
- What does the lifecycle of an issue look like? (triage → backlog → sprint → in progress → review → done)
- Who creates issues? (PMs, engineers, anyone?)
- How are bugs vs features vs chores distinguished?
- Sprint/cycle cadence? (weekly, biweekly, continuous, etc.)
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.
- 3d ago First seen · 115 lines · 41 tokens per session scan A fc8da2e94663
q-which-process 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 931 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…