What is q-setup-tools?

A setup assistant for the command-line tools and MCP servers listed in `.quiddity/tools.json`. It checks whether recommended tools are installed and guides setup for anything missing.

Use it to inspect a project’s tool list, verify installed command-line programs, check configured MCP servers, and set up missing dependencies.

It removes the guesswork from preparing a project’s development tools and lets you skip tools you do not want to install.

q-setup-tools — Skill for Claude Code and Codex by jlong/quiddity

Install

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.

Any agent

npx skills add jlong/quiddity --skill q-setup-tools

Clone the repo

git clone --depth 1 https://github.com/jlong/quiddity

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-tools/github.svg)](https://agentmods.dev/skills/jlong/quiddity/q-setup-tools)

Your own site

<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-tools"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-tools/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/jlong/quiddity/q-setup-tools"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-setup-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 768 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00768
Opus 5.5	$0.00016	$0.00307
Sonnet 5.5	$0.00008	$0.00154
Haiku 4.5	$0.00004	$0.00077

Measured 2mo ago against content hash 1d98143bcbaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

q-setup-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 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.

skills/q-setup-tools/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/q-setup-tools

You are helping the user set up the CLIs and MCPs needed by their project's tools. Your job is to check what's already installed, guide setup for anything missing, and let the user skip anything they don't want.

Prerequisites

.quiddity/tools.json must exist. If it doesn't, tell the user to run /q-which-tools first and stop.

Reference data

tool-registry.json (in the same directory as this skill) maps tool names to recommended CLIs and MCPs. Load it at the start.

Process

Read tools.json. Collect all unique tool values from every category.
Match against the registry. For each tool name found in tools.json, look it up in tool-registry.json. Tools not in the registry are fine — just note them as "no setup recommendations available" and move on.
Check what's already installed. For each matched tool:
- CLIs: Run the verifyCommand from the registry. If it succeeds, the CLI is already installed. If it fails or the command is not found, it needs setup.
- MCPs: Check whether the MCP server is already configured. Look in .claude/settings.json, .mcp.json, or ~/.claude.json for an existing entry matching the package name.

Present a summary. Show the user a table of all tools, what's installed vs. what's missing. For tools with only a notes field in the registry, display the note. For example:

Tool             CLI         MCP
GitHub           gh (ok)     —
GitHub Actions   (no setup needed — runs in CI)
Linear           —           Linear MCP (not found)

Walk through missing items. For each tool with something missing:
- Explain what the CLI or MCP does and why it's useful.
- Offer to install it or let the user skip.
- For CLIs: Run the installCommand from the registry. After installation, run verifyCommand to confirm it worked. If the CLI needs authentication (like gh auth login), walk the user through it.
- For MCPs: Help the user add the MCP server configuration. Use claude mcp add with the package name from the registry, or guide them to add it manually. Link to the docsUrl for reference.

Read the full file on GitHub · 73 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

tool-registry.json 2.4 KB

Changes

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 · 73 lines · 40 tokens per session scan A 1d98143bcbaf

Subscribe to this mod's changes

q-setup-tools 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 768 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.

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.