brief

brief is a skill for Claude Code, Codex from rickywo/Formic. It costs 17 tokens per session (413 once invoked), scanned A, original, MIT.

A task-specification writer that creates a README.md describing a requested software feature. It first examines the project so the document matches its technology and existing conventions.

In plain words
What is it for?
It helps document a Formic task with an overview, goals, capabilities, non-goals, and requirements. It is used when a team needs a clearer implementation brief.
Why use it?
A short task description often leaves goals, requirements, and boundaries unclear. This turns it into a shared specification that developers can use before implementation.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/rickywo/formic/brief
Any agent
npx skills add rickywo/Formic --skill brief
Clone the repo
git clone --depth 1 https://github.com/rickywo/Formic

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.

agentmods badge for brief

README.md
[![agentmods](https://agentmods.dev/badge/skills/rickywo/formic/brief.svg)](https://agentmods.dev/skills/rickywo/formic/brief)
Your own site
<a href="https://agentmods.dev/skills/rickywo/formic/brief"><img src="https://agentmods.dev/badge/skills/rickywo/formic/brief.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00017 $0.00413
Opus 5 $0.00009 $0.00206
Sonnet 5 $0.00003 $0.00083
Haiku 4.5 $0.00002 $0.00041

Measured 5d ago against content hash 95a62266d498, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 5d 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/brief/SKILL.md · 73 lines

What it actually says

Brief Skill - Generate Task Specification

You are a senior Technical Project Manager. Your task is to generate a feature specification document for the following task.

Task Title: $TASK_TITLE

Task Context/Description: $TASK_CONTEXT

Output Location: $TASK_DOCS_PATH/README.md


Instructions

  1. First, explore the project codebase to understand:

    • The tech stack and frameworks used
    • Existing architectural patterns
    • Coding conventions and standards
    • If kanban-development-guideline.md exists, read it for project-specific rules
  2. Generate a README.md file with the following structure:

# [Task Title]

## Overview
[A brief 2-3 sentence introduction to what this task accomplishes and why it's needed.]

## Goals
- [Primary objective 1]
- [Primary objective 2]
- [Primary objective 3]

## Key Capabilities
- [Main functionality 1]
- [Main functionality 2]
- [Main functionality 3]

## Non-Goals
- [What is explicitly out of scope 1]
- [What is explicitly out of scope 2]

## Requirements
- [Technical requirement 1]
- [Technical requirement 2]
- [Non-technical requirement if applicable]
  1. Write the generated content to: $TASK_DOCS_PATH/README.md

Guidelines

  • Focus on the 'what' and 'why', NOT the 'how' (implementation details come in PLAN.md)
  • Be specific to this project's context - reference actual files, patterns, or conventions you discover
  • Keep it concise - each section should have 3-5 bullet points maximum
  • Goals should be measurable outcomes
  • Non-Goals help prevent scope creep
  • Requirements should be verifiable

Output

Write the README.md file to the specified path. Do not output anything else.

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. 5d ago First seen · 73 lines · 17 tokens per session scan A 95a62266d498

Subscribe to this mod's changes

brief is a skill published in the GitHub repository rickywo/Formic (41 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 413 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

analyze-performance-traces

Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…

tutti-os/tutti · 127 tokens

tutti-test-audit

Audit, design, write, materially revise, or remove Tutti tests. Use whenever Codex changes or reviews unit, component, conformance, integration, regression, platform, or repository tests; enforce a protected product contract, credible failure, correct owning boundary, negative-control evidence, overlap review…

tutti-os/tutti · 74 tokens

tutti-agent-workspace-app

Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging…

tutti-os/tutti · 106 tokens

assimilate-popular-workflows

This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…

a5c-ai/babysitter · 110 tokens

frontmatter-parsing

YAML frontmatter parsing and manipulation for .planning/ documents. Provides read, write, update, query, and validation operations on frontmatter blocks in GSD markdown artifacts.

a5c-ai/babysitter · 40 tokens

babysit-babysitter-issues

This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.

a5c-ai/babysitter · 69 tokens