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 jqaisystems/jqai-ai-skills --skill discovery-briefgit clone --depth 1 https://github.com/jqaisystems/jqai-ai-skillsWrote 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/jqaisystems/jqai-ai-skills/discovery-brief)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/discovery-brief"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/discovery-brief/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/jqaisystems/jqai-ai-skills/discovery-brief"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/discovery-brief.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.00076 | $0.00710 |
| Opus 5.5 | $0.00030 | $0.00284 |
| Sonnet 5.5 | $0.00015 | $0.00142 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
discovery-brief 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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discovery Brief
A project priced before discovery is a project scoped by hope. This skill runs the discovery conversation and turns the answers into two working documents: the brief (the project's source of truth) and a strategy starter (the first thinking pass).
This is the interview counterpart to a client-facing intake form: the client-intake-builder skill generates an HTML questionnaire the CLIENT fills in alone; this skill interviews YOU (or processes the client's answers) and writes the documents.
Step 1: Read what already exists
Before asking anything, read whatever the user points at: an existing brief, intake form answers, emails, meeting notes, the client's website. Never ask a question the material already answers.
Step 2: Interview across seven areas
Ask in small batches, not twenty questions at once. Skip known answers.
- Business: what the client does, how they make money, what stage they are at (new, rebrand, growing).
- Audience: who buys now, who they WANT to buy, price positioning (budget, mid, premium).
- Competitors: two or three names, what the client envies or hates about each.
- Personality: three to five adjectives the brand should own, two or three it must never be.
- Style direction: references they love, styles or colours that are off-limits.
- Deliverables: exactly what the project produces (logo, identity system, guidelines, packaging, website, motion, other).
- Timeline and budget: deadline and budget range, mapped against the user's own tiers if a pricing config exists (see the
proposal-writerskill).
Step 3: Write the two documents
The brief (default Brief.md in the client's folder): status, started date, scope checklist, and every answer organized under the seven areas. Keep the client's own words where they are vivid; quote them. Unknowns stay visible as open items, never filled with guesses.
The strategy starter (default Strategy/01_Strategy.md):
# <Client> Strategy Starter
## Positioning (draft)
One sentence: for WHOM, the brand is WHAT, unlike COMPETITOR because REASON.
## Audience snapshot
## Competitive picture
What competitors do visually or verbally, and where the gap is.
## Personality and tone
The adjectives, and what each means in practice.
## Direction hypotheses
Two or three distinct directions worth exploring, two lines each.
## Open questions
Everything discovery did not answer.
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.
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.
- 1mo ago First seen · 67 lines · 76 tokens per session scan A 73b307b7f7ac
discovery-brief is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 76 tokens to every session and 710 once invoked, about $0.0003 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
reins
Drive the user's real, logged-in browser from the shell via the reins CLI. Because it's their actual browser, every site is already authenticated — so you can scrape behind logins, read cookies/tokens/localStorage, watch and replay live API traffic, call a site's own API as the signed-in user, and…
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
spring-boot-team-harness
Use when a team wants every developer's coding agent (Claude Code or Codex) to follow the same rules on a Maven Spring Boot 4 repository: setting up AGENTS.md, guardrails, shared agent settings, or build and CI checks that agents must pass before code merges. It adds ./mvnw verify gates that fail on null-safety bugs…
agent-wiki
Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.