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 synaptiai/synapti-marketplace --skill capability-discoverygit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/capability-discovery)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/capability-discovery"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/capability-discovery/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/synaptiai/synapti-marketplace/capability-discovery"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/capability-discovery.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.00077 | $0.01078 |
| Opus 5 | $0.00039 | $0.00539 |
| Sonnet 5 | $0.00015 | $0.00216 |
| Haiku 4.5 | $0.00008 | $0.00108 |
Grade A, and why
capability-discovery 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 today.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capability Discovery
Contract
Iron law: discover before assuming — never hardcode tool availability; scan the environment first. Invoked once per command run, before any quality or verification phase: /flow:start Phase 1, /flow:pr pre-flight, /flow:address before verification, /flow:resolve step 1c, /flow:setup Phase 1, /flow:design and /flow:brainstorm EXPLORE, and the test-runner agent. Returns the six-section markdown report below (Agents Available, Skills Available, Quality Commands, Tech Stack, Verification Capabilities, LSP Capabilities). The calling command stores the output for later phases and does not re-invoke it within the same run. Permitted skips: the markdown-only early exit (no tech-stack file and no quality commands in CLAUDE.md) and LSP probing when lsp.enabled is false.
Detection Order
Steps 1-5 are independent — run them simultaneously with parallel tool calls.
-
Agents:
Glob ".claude/agents/*.md"(project) and"plugins/*/agents/*.md"(plugin); parse source, name (filename without.md), description (frontmatter). -
Skills:
Glob ".claude/skills/*/SKILL.md"and"plugins/*/skills/*/SKILL.md"; parse source, name (parent directory), description. -
Commands:
Glob ".claude/commands/*.md"and"plugins/*/commands/*.md"; parse source, name, description. -
Quality commands from CLAUDE.md —
.claude/CLAUDE.mdfirst, thenCLAUDE.md:grep -E "(npm|pnpm|yarn|bun|ruff|pytest|go |cargo |make )" "$CLAUDE_MD" -
Tech stack by indicator file:
package.json→ node,tsconfig.json→ typescript,pyproject.toml→ python,Gemfile→ ruby,go.mod→ go,Cargo.toml→ rust,Makefile→ makefile.
Early exit — markdown-only: no tech-stack file AND no quality commands in CLAUDE.md → report Quality Commands "No code-related quality commands applicable", Tech Stack "Markdown-only project", skip Step 6.
- Verification capabilities:
ls verify.sh scripts/verify* playwright.config.* cypress.config.* 2>/dev/null. - LSP capabilities: pre-check
lsp.enabled(defaulttrue; iffalse, report every featureDisabled). ProbedocumentSymbol,hover,goToDefinition,findReferences,goToImplementationagainst one representative source file for the detected stack, each bounded bylsp.timeout(default 5000 ms); inferdiagnosticsAvailable whendocumentSymbolsucceeds. Procedure and result rules:references/lsp-capability-probes.md.
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.
- today Changed · -85 lines 5a7ec1980cc9
- 7d ago First seen · 159 lines · 77 tokens per session scan A 0035aae82ca0
capability-discovery is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 1,078 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
step4-archive-spec
Archive a completed spec — moves it to specs-archived and blocks agent access.
plan-product
Define product mission, vision, target users, and technology stack.