agentmods.dev

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.

In plain words
What is it for?
Use it to inspect a project’s tool list, verify installed command-line programs, check configured MCP servers, and set up missing dependencies.
Why use it?
It removes the guesswork from preparing a project’s development tools and lets you skip tools you do not want to install.

Skill for Claude CodeCodex

5 5mo ago A scan 40 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/jlong/quiddity/q-setup-tools
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.

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. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.00768
Opus 5 $0.00020 $0.00384
Sonnet 5 $0.00008 $0.00154
Haiku 4.5 $0.00004 $0.00077

Measured 3d ago against content hash 1d98143bcbaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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

  1. Read tools.json. Collect all unique tool values from every category.

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

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

  4. 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)

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

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.

  1. 3d 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 5mo ago), licensed MIT. It adds 40 tokens to every session and 768 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.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

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.

microsoft/vscode · 51 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

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…

microsoft/vscode · 71 tokens