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-setup-new-issuegit 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-new-issue)<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-new-issue"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-new-issue/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-new-issue"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-new-issue.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.00049 | $0.00563 |
| Opus 5.5 | $0.00020 | $0.00225 |
| Sonnet 5.5 | $0.00010 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
q-setup-new-issue 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup /new-issue
You are generating a custom /new-issue skill for the user's project.
Required categories
This skill needs the following tools.json categories: issues
Process
-
Ensure tools are configured. Check if
.quiddity/tools.jsonexists and contains theissuescategory. If not, run/q-which-tools issuesto configure it. -
Read the configuration. Load all available Quiddity context:
.quiddity/project.md— project structure, tech stack, issue templates.quiddity/process.md— issue workflow and conventions.quiddity/tools.json— extract theissuescategory
-
Ask skill-specific questions not covered by tools.json:
- Should the skill accept a description as an argument?
(e.g.,
/new-issue Add dark mode support) - Do issues need acceptance criteria generated automatically?
- Any standard sections? (description, steps to reproduce, expected behavior)
- Any issue templates already in use?
- Auto-assign issues to the creator?
- For UI-related issues, should the skill generate ASCII wireframes to illustrate the proposed change? (Great for making layout and component ideas concrete before implementation.)
- Should the skill accept a description as an argument?
(e.g.,
-
Generate the skill. Write a complete
/new-issueSKILL.md to the project's skills directory. The generated skill should:- Accept a plain-English description (via
$ARGUMENTSor interactive prompt) - Generate a structured issue with proper title, description, and acceptance criteria based on the user's conventions
- Apply the right labels, priority, and milestone using the configured tracker
- Create the issue via MCP or CLI based on the tool in tools.json
- Return the issue identifier and URL
- Reference
.quiddity/tools.jsonfor all tool-specific configuration
- Accept a plain-English description (via
-
Show the generated skill to the user and ask for confirmation before finalizing.
Generated skill template
The generated /new-issue 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.
- 2mo ago First seen · 65 lines · 49 tokens per session scan A de64cca6f988
q-setup-new-issue is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 7mo ago), licensed MIT. It adds 49 tokens to every session and 563 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,"…