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 yuri-semenenko/ai-engineering-workspace --skill context-briefgit clone --depth 1 https://github.com/yuri-semenenko/ai-engineering-workspaceWrote 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/yuri-semenenko/ai-engineering-workspace/context-brief)<a href="https://agentmods.dev/skills/yuri-semenenko/ai-engineering-workspace/context-brief"><img src="https://agentmods.dev/badge/skills/yuri-semenenko/ai-engineering-workspace/context-brief.svg" alt="Measured on agentmods" 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.00036 | $0.00308 |
| Opus 5 | $0.00018 | $0.00154 |
| Sonnet 5 | $0.00007 | $0.00062 |
| Haiku 4.5 | $0.00004 | $0.00031 |
Grade A, and why
context-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 8d 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.
What it actually says
Context Brief
Create a bounded brief that lets another pass work from evidence instead of chat history.
Process
- State the goal in one or two sentences.
- Capture constraints: scope, non-goals, deadlines, risky areas, and user preferences that affect execution.
- List relevant files, commands, tickets, PRs, docs, and external references with why each matters.
- Summarize observed facts separately from assumptions.
- Identify open questions that block safe implementation or review.
- Recommend the next action: implement, investigate, review, ask the user, or stop.
Output
Use this shape unless the user asks for another format:
## Goal
<what needs to happen>
## Constraints
- <scope, non-goals, verification, timing, ownership>
## Evidence
- `<path or command>` - <why it matters>
## Facts
- <verified fact>
## Assumptions
- <assumption and why it is acceptable or risky>
## Open Questions
- <question or "None">
## Recommended Next Step
<one concrete next action>
Keep the brief compact. Do not paste large file contents, transcripts, or full diffs. Link to local files and quote only the lines needed to make the handoff actionable.
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.
- 8d ago First seen · 47 lines · 36 tokens per session scan A de38f0d5d2f5
context-brief is a skill published in the GitHub repository yuri-semenenko/ai-engineering-workspace (1 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 308 once invoked, about $0.0002 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.
Other skills, from other repositories
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
My Skill
Content here.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.