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-scan-projectgit 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-scan-project)<a href="https://agentmods.dev/skills/jlong/quiddity/q-scan-project"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-scan-project/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-scan-project"><img src="https://agentmods.dev/badge/skills/jlong/quiddity/q-scan-project.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.00030 | $0.01027 |
| Opus 5.5 | $0.00012 | $0.00411 |
| Sonnet 5.5 | $0.00006 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
q-scan-project 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/q-scan-project
You are scanning the user's project to understand its structure and document what you find. Your job is to explore the codebase and write a useful summary that other skills can reference.
Process
-
Check for existing project.md. If
.quiddity/project.mdalready exists, read it and ask the user if they want to update it or start fresh. -
Scan the project. Look for the following and note what you find:
Key documentation files
- README, README.md
- ARCHITECTURE.md, DESIGN.md
- CONTRIBUTING.md
- CHANGELOG.md
- ROADMAP.md
- CLAUDE.md, .cursorrules, or other agent configuration
- Any docs/ or documentation/ directory
Project configuration
- package.json, Cargo.toml, pyproject.toml, go.mod, Gemfile, etc.
- What language(s) and framework(s) does the project use?
- What package manager? (npm, pnpm, yarn, bun, cargo, pip, etc.)
- Monorepo structure? (workspaces, lerna, turborepo, etc.)
Source structure
- Where does source code live? (src/, lib/, app/, etc.)
- Entry points (main files, index files, etc.)
- Test directory structure (tests/, tests/, spec/, etc.)
CI/CD and configuration
- .github/workflows/, .circleci/, Jenkinsfile, etc.
- Docker files (Dockerfile, docker-compose.yml)
- Deployment configuration (vercel.json, fly.toml, etc.)
Existing conventions
- .editorconfig, .prettierrc, .eslintrc, etc.
- PR templates (.github/pull_request_template.md)
- Issue templates (.github/ISSUE_TEMPLATE/)
- CODEOWNERS
Plans and specs
- Any planning documents, RFCs, ADRs (architecture decision records)
- Spec files or design documents
- TODO files
-
Ask clarifying questions. If anything is ambiguous, ask the user:
- Is there anything important about the project structure not captured above?
- Are there any conventions or patterns that aren't obvious from the files?
-
Set up architecture reference. Other skills (like
/next-task) read.quiddity/architecture.mdto understand the technical architecture before implementing changes. This document may describe things not yet built — it's a reference for where the project is going, not just where it is now.
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 · 118 lines · 30 tokens per session scan A 375fdf4377a7
q-scan-project is a skill published in the GitHub repository jlong/quiddity (5 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 1,027 once invoked, about $0.0001 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
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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.