A skill for turning locally saved briefs into tickets. A brief can contain a screen recording, annotated screenshot, voice transcript, or written description.

Use it to process briefs from the Chrome extension into Linear, Jira, GitHub, or Notion tickets, then clean up the processed brief.

It gathers the user's report from the available files and files a ticket in the requested project system without assuming every brief has the same contents.

brief — Skill for Claude Code and Codex by razi2001

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 razi2001/brief --skill skill

Clone the repo

git clone --depth 1 https://github.com/razi2001/brief

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

README.md

[![agentmods](https://agentmods.dev/badge/skills/razi2001/brief/skill/github.svg)](https://agentmods.dev/skills/razi2001/brief/skill)

Your own site

<a href="https://agentmods.dev/skills/razi2001/brief/skill"><img src="https://agentmods.dev/badge/skills/razi2001/brief/skill/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/razi2001/brief/skill"><img src="https://agentmods.dev/badge/skills/razi2001/brief/skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,512 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.

Model	Per session	Once invoked
Fable 5.1	$0.00111	$0.01512
Opus 5.5	$0.00044	$0.00605
Sonnet 5.5	$0.00022	$0.00302
Haiku 4.5	$0.00011	$0.00151

Measured 1mo ago against content hash 8afcc427e344, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

extension/skill/SKILL.md · 75 lines

How it starts

The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Brief — Router

Briefs are captured locally and stored in ~/Downloads/brief/. Each is either:

a .zip file (brief-<id>.zip) — yet-to-be-extracted
a folder (brief-<id>/) after extraction

A brief can contain any combination of these (check brief.json to see which):

A recording — recording.webm + sampled keyframes/*.png + a voice transcript. (Recording briefs.)
An annotated screenshot — screenshot.png. Any red markings on it were drawn by the user to point at where the issue is. Treat the red as the focus indicator, not as part of the page UI. (brief.json.hasScreenshot / screenshotAnnotated.)
A text description — brief.json.description, the user's own words about the issue.

So a brief might be a full recording, OR just a screenshot with a red circle, OR just a sentence of text, OR a mix. Use whatever is present. Never assume a recording exists — read brief.json first.

Briefs only exist for one purpose: to become Linear/Jira/GitHub/Notion tickets. Your job is to file the ticket — efficiently, without unnecessary questions — and then clean up.

Step 1 — Identify the action

The user's prompt will be one sentence containing one of:

User says…	Load
"process my inbox" / "briefs X, Y, Z"	`playbooks/inbox.md`
"turn brief X into a ticket" (or similar)	`playbooks/ticket.md`

If the prompt names multiple brief IDs or contains the word "inbox", use inbox.md — that playbook orchestrates the others. Otherwise use ticket.md.

Step 2 — Read the playbook

The playbooks live next to this file, in the same skill/playbooks/ folder inside the brief. Load the matching one (skill/playbooks/<name>.md) and follow it. It contains all the rules: how to read the brief files, how to handle screenshots/recordings/text, how to infer the team/repo, how to embed images inline, etc.

Read the full file on GitHub · 75 lines

Files

What ships with it

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

1mo ago First seen · 75 lines · 0 tokens per session scan A 8afcc427e344

Subscribe to this mod's changes

brief is a skill published in the GitHub repository razi2001/brief (21 stars, last pushed 4mo ago), licensed MIT. It adds 111 tokens to every session and 1,512 once invoked, about $0.0004 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-30.

Project management ai-agents bug-reporting chrome-extension linear voice

linear-cli

Manage Linear issues from the command line using the linear cli. This skill allows automating linear management.

schpet/linear-cli · 23 tokens

cyrus-setup-repository

Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.

cyrusagents/cyrus · 25 tokens

summarize

Format a final summary message for Linear. Your output is automatically streamed to the Linear agent session — just format it well, do not post it yourself.

cyrusagents/cyrus · 34 tokens

orient

Always-on. How the harness talks to the person: STE-style short sentences, every answer understandable on its own, technical or with analogies by the profile, and a ladder (text → diagram → HTML page → video on request) when the person does not follow. Closes every turn with the brújula. Fires on 'no entiendo'…

ericrisco/rsc-harness · 132 tokens

linearis

Manage Linear.app work from the command line with the linearis CLI (bins linearis / linear), which outputs JSON: issues/tickets, projects, cycles (sprints), milestones, initiatives (roadmap), documents, labels, teams, users, and issue discussions/comments. Use when the user mentions Linear, a ticket identifier like…

linearis-oss/linearis · 111 tokens

cyrus-setup-linear

Create a Linear OAuth application and configure Cyrus to use it — supports agent-browser automation or guided manual setup.

cyrusagents/cyrus · 27 tokens