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 jlong/quiddity --skill q-setupgit 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)<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup/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/jlong/quiddity/q-setup"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup.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.00040 | $0.00609 |
| Opus 5.5 | $0.00016 | $0.00244 |
| Sonnet 5.5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
q-setup 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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/q-setup
You are running the full Quiddity setup flow for the user's project. This will discover their process and tools, then generate all three build-loop skills.
Process
-
Welcome the user. Briefly explain what Quiddity does: it will scan their project, learn about their development process and tools, set up CLIs and MCPs, then generate three custom skills (
/new-issue,/next-task,/approve) tailored to their project. -
Run /q-scan-project to scan the project structure. This documents key files, tech stack, conventions, and project layout in
.quiddity/project.md. -
Run /q-which-process to discover the user's SDLC. This captures their branching strategy, code review process, issue workflow, and other conventions in
.quiddity/process.md. It can referenceproject.mdfor context. -
Run /q-which-tools with all categories needed across the three skills:
/q-which-tools issues source-control ci prBecause
/q-which-processhas already run,/q-which-toolscan reference.quiddity/process.mdto pre-fill answers and ask smarter questions. -
Run /q-setup-tools to walk through CLI and MCP setup for each tool discovered in the previous step. This checks what's already installed and helps set up anything missing.
-
Run /q-setup-new-issue to generate the
/new-issueskill. Since project.md, process.md, and tools.json are already populated, this will skip the interviews and go straight to skill-specific questions. -
Run /q-setup-next-task to generate the
/next-taskskill. -
Run /q-setup-approve to generate the
/approveskill. -
Summarize. Show the user what was generated:
- The location of
.quiddity/project.md,.quiddity/process.md, and.quiddity/tools.json - The three generated skills and their locations
- A quick reminder of how to use each skill:
/new-issue [description]— create a new issue/next-task— pick up and implement the next task/approve [pr-number]— merge an approved PR
- Suggest they review each generated skill and tweak as needed
- Remind them to commit
.quiddity/and the generated skills to source control so the whole team shares the same configuration
- The location of
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.
- 2mo ago First seen · 54 lines · 40 tokens per session scan A efb2ea16c1a9
q-setup is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 7mo ago), licensed MIT. It adds 40 tokens to every session and 609 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…