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 craigcossairt/trellis --skill daily-briefgit clone --depth 1 https://github.com/craigcossairt/trellisWrote 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/craigcossairt/trellis/daily-brief)<a href="https://agentmods.dev/skills/craigcossairt/trellis/daily-brief"><img src="https://agentmods.dev/badge/skills/craigcossairt/trellis/daily-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/craigcossairt/trellis/daily-brief"><img src="https://agentmods.dev/badge/skills/craigcossairt/trellis/daily-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.00060 | $0.00592 |
| Opus 5 | $0.00030 | $0.00296 |
| Sonnet 5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
daily-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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are producing the day's brief: a ranked answer to "what should I work on today?" grounded in the project's actual state, not vibes.
Gather (use what exists, skip what doesn't - never fail on a missing source)
- Git state - commits since yesterday (
git log --since=yesterday --oneline --all), current branch, uncommitted changes, unpushed commits, open PRs (gh pr list). - Open issues -
gh issue list(or the project's tracker via its MCP server if one is connected - check AGENTS.md for which tracker this project uses). - Project docs - the 5 newest entries in
docs/decision-log.mdand any gotchas added in the last week, for context on where the project's head is. - Optional signals - IF other MCP servers are connected (email, analytics, error tracking), pull their top items. Never error or nag about sources that aren't connected; a git-only brief is still a good brief.
Rank
Score candidate work by, in order:
- Unblocks something - work that other work (or a person) is waiting on
- Deadline proximity - anything dated
- Momentum - in-progress work close to done beats starting something new
- Quick wins - under-30-minute items worth batching
Flag separately anything that needs a HUMAN decision before an agent can act on it.
Output format
Keep the whole brief under ~30 lines:
# Daily Brief - {date}
## Recommended focus (top 3)
1. {item} - {one-line why it's ranked here}
2. ...
3. ...
## Needs your decision
- {item} - {what's blocked on the human} (omit section if empty)
## Also on the board
- {compressed list of remaining open items}
## Since yesterday
- {commits/PRs merged, one line each}
Notes
- Be opinionated in the ranking - a brief that lists everything equally decides nothing.
- If the project has no tracker and no recent commits, say so and suggest the single most useful next step instead of inventing a board.
- This skill can be scheduled (e.g. a daily task that runs it and saves the output) - see your harness's scheduling features. Start by running it manually; schedule it once you trust it.
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.
- 11d ago First seen · 61 lines · 60 tokens per session scan A ee688de3639b
daily-brief is a skill published in the GitHub repository craigcossairt/trellis (4 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 592 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-08-31.
Other skills, from other repositories
progress
Compare the repo's real state against the roadmap, acknowledge progress, log the session, and plan what's next. Use when the user asks where things stand, what to do next, returns after a break, or seems stuck or demotivated.
lov-rename-project
A project-renaming workflow that updates a product or repository name across source files, configuration, and documentation. It produces a reviewable plan and preserves compatibility-sensitive names and references where needed.
lov-repo2docs
Turn any folder of source material — a code repository, a pile of articles, a mixed knowledge dump with images — into a professional, polished Fumadocs (Next.js) documentation website, then deploy it to https://{product-id}.example.com/docs. Works by reading the folder one unit at a time and incrementally growing and…
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
lov-proposal
Generate complete business proposals for client projects from requirements.
ainb-fleet
Fleet orchestration overview — the ainb fleet ... Rust subcommand namespace for driving every claude session on the host. Routes to the sub-skills (ainb-spawn / standup / broadcast / sequence / needs / daemon / atc). Invoke this for an at-a-glance map of what fleet can do; reach for the specific sub-skill for the verb…