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-next-tasknpx skills add jlong/quiddity --skill q-setup-next-taskgit 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-next-task)<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-next-task"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-next-task.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.00057 | $0.00699 |
| Opus 5 | $0.00028 | $0.00349 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
q-setup-next-task 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup /next-task
You are generating a custom /next-task skill for the user's project.
Required categories
This skill needs the following tools.json categories: issues, source-control, ci
Process
-
Ensure tools are configured. Check if
.quiddity/tools.jsonexists and contains theissues,source-control, andcicategories. For any missing categories, run/q-which-toolswith those categories (e.g.,/q-which-tools issues source-control ci). -
Read the configuration. Load all available Quiddity context:
.quiddity/project.md— project structure, tech stack, test commands, source directories, entry points.quiddity/process.md— branching strategy, code review process, commit conventions.quiddity/tools.json— extract theissues,source-control, andcicategories.quiddity/architecture.md— technical architecture and design direction (if it exists)
-
Ask skill-specific questions not covered by tools.json:
- How should the next task be selected? (highest priority, oldest, specific label, assigned to me, etc.)
- Should the skill assign the issue to the current user?
- Any PR title/description conventions beyond what's in tools.json?
- Should it run local checks before pushing?
- What should it do when blocked? (report back, skip to next task, etc.)
-
Generate the skill. Write a complete
/next-taskSKILL.md to the project's skills directory. The generated skill should:- Query the issue tracker for the highest-priority available task using the configured tool and filters
- Assign the issue and move it to the "In Progress" state
- Create a branch following the configured naming convention
- If
.quiddity/architecture.mdexists, read it before implementing to understand design direction, constraints, and patterns — it may describe things not yet built that are relevant to the current task - Implement the changes described in the issue
- Run local CI checks before pushing
- Open a PR with the right format and link it to the issue
- Update the issue status
- Include judgment — if something blocks the task, report back instead of plowing ahead
- Reference
.quiddity/tools.jsonfor all tool-specific configuration
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 · 76 lines · 57 tokens per session scan A 24fae3b6d038
q-setup-next-task is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 699 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.
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…