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 WyvernCW/Monich --skill project-briefgit clone --depth 1 https://github.com/WyvernCW/MonichWrote 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/wyverncw/monich/project-brief)<a href="https://agentmods.dev/skills/wyverncw/monich/project-brief"><img src="https://agentmods.dev/badge/skills/wyverncw/monich/project-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/wyverncw/monich/project-brief"><img src="https://agentmods.dev/badge/skills/wyverncw/monich/project-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.00055 | $0.00844 |
| Opus 5 | $0.00028 | $0.00422 |
| Sonnet 5 | $0.00011 | $0.00169 |
| Haiku 4.5 | $0.00006 | $0.00084 |
Grade A, and why
project-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- project-brief — 100% identical, 0 lines differ
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.
Project Brief Template
Use this template for weekly / periodic digests that should feel like a hand-assembled reporter's notebook — issue-numbered, taped, clipped, ruled, with a clear physical metaphor.
Use When
- The artifact is a recurring digest (周报 / VOL.NN / Issue N) with multiple grouped entries.
- Sections include: new features, optimizations, bug fixes, links, notes — i.e. a changelog-shaped narrative.
- The voice is product-team or editorial-team-internal, not corporate.
- The deliverable will be exported / shared as a high-res image or PDF, not just a scrolling page.
Avoid When
- The content is a one-off announcement (use a social card or blog-post).
- The audience expects a corporate formal report — this is intentionally crafty and warm.
- The user wants a presentation / deck (use
ppt/). - The content is a marketing landing — wrong carrier entirely.
Required Reading
Read this SKILL.md first. Do not read 清言周报-VOL18-notebook.html by default.
Read the pattern only when you need concrete geometry — spiral hole spacing, tape angle and deckle, binder-clip placement, receipt-grid pattern, the 31px ruled baseline. Extract patterns; do not copy placeholder issue numbers, dates, feature names, or class names wholesale.
Design Strategy
Lock the issue's spine before placing decoration:
- Masthead — logo + date strip + 1-paragraph intro.
- Issue mark — cobalt tape with VOL.NN + binder clip.
- Table of contents — three-column grid pointing to numbered sections.
- Sections — each with a kicker (uppercase Spanish / English label) + Chinese title + indexed entries.
- One "physical" highlight block — receipt for optimizations, taped Polaroid for a feature, mint folder tab for an announcement.
- Closing lockup + colophon — QR / ticket / page-number metadata.
Each issue should follow the same spine — that's how a weekly builds identity over time.
Layout Bias
Prefer:
- mixed serif (FlyFlowerSong / Noto Serif SC) + sans (Noto Sans SC) + mono (JetBrains Mono) — each carries a role
- ruled baseline grid for body copy; entries align to it
- dashed dividers between entries, not solid rules
- one or two "physical" elements per page (tape / clip / receipt / folder tab) — not all of them at once
- index numbers (01 / 02 / 03) on entries; uppercase Latin kickers above CJK section titles
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 · 75 lines · 55 tokens per session scan A 4e019b45ac36
project-brief is a skill published in the GitHub repository WyvernCW/Monich (3 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 844 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.