discovery-brief

discovery-brief is a skill for Codex from jqaisystems/jqai-ai-skills. It costs 76 tokens per session (710 once invoked), scanned A, original, MIT.

A guided interview process for understanding a new client project and producing a project brief plus an initial strategy document. It covers the business, audience, competitors, brand personality, and other planning areas.

In plain words
What is it for?
It helps run discovery interviews, collect missing project information in small groups, complete a working brief, and create a first strategy outline.
Why use it?
It prevents projects from being priced or planned around guesses. It also avoids asking questions that existing briefs, emails, notes, or websites have already answered.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It helps run discovery interviews, collect missing project information in small groups, complete a working brief, and create a first strategy outline.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jqaisystems/jqai-ai-skills/discovery-brief
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 jqaisystems/jqai-ai-skills --skill discovery-brief
Clone the repo
git clone --depth 1 https://github.com/jqaisystems/jqai-ai-skills

Made for: 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.

agentmods badge for discovery-brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/discovery-brief/github.svg)](https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/discovery-brief)
Your own site
<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.

agentmods 80×15 button for discovery-brief

Your own site · 80×15
<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>
Per session 76 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 710 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00076 $0.00710
Opus 5 $0.00038 $0.00355
Sonnet 5 $0.00015 $0.00142
Haiku 4.5 $0.00008 $0.00071

Measured 12d ago against content hash 73b307b7f7ac, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 12d 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/discovery-brief/SKILL.md · 67 lines

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.

  1. Business: what the client does, how they make money, what stage they are at (new, rebrand, growing).
  2. Audience: who buys now, who they WANT to buy, price positioning (budget, mid, premium).
  3. Competitors: two or three names, what the client envies or hates about each.
  4. Personality: three to five adjectives the brand should own, two or three it must never be.
  5. Style direction: references they love, styles or colours that are off-limits.
  6. Deliverables: exactly what the project produces (logo, identity system, guidelines, packaging, website, motion, other).
  7. Timeline and budget: deadline and budget range, mapped against the user's own tiers if a pricing config exists (see the proposal-writer skill).

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.

Read the full file on GitHub · 67 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. 12d ago First seen · 67 lines · 76 tokens per session scan A 73b307b7f7ac

Subscribe to this mod's changes

discovery-brief is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 710 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-08-31.

Related

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…

karnstack/reins · 98 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

skill-curator

A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.

laolaoshiren/claude-code-skills-zh · 75 tokens

git-workflow

A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.

laolaoshiren/claude-code-skills-zh · 73 tokens

i18n-helper

A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.

laolaoshiren/claude-code-skills-zh · 33 tokens

review-plan

Review a plan by running internal reviews and a peer review in parallel and returning combined findings. Use when the user asks to "review my plan", "check my plan", "critique my plan", or wants feedback on a plan.

tobihagemann/turbo · 50 tokens