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 pyranthus-hq/mora --skill daily-brief-loopgit clone --depth 1 https://github.com/pyranthus-hq/moraWrote 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/pyranthus-hq/mora/daily-brief-loop)<a href="https://agentmods.dev/skills/pyranthus-hq/mora/daily-brief-loop"><img src="https://agentmods.dev/badge/skills/pyranthus-hq/mora/daily-brief-loop/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/pyranthus-hq/mora/daily-brief-loop"><img src="https://agentmods.dev/badge/skills/pyranthus-hq/mora/daily-brief-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.02711 |
| Opus 5 | $0.00032 | $0.01355 |
| Sonnet 5 | $0.00013 | $0.00542 |
| Haiku 4.5 | $0.00006 | $0.00271 |
Grade A, and why
daily-brief-loop 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Brief Loop
Requires the local mora CLI on PATH and shell execution with observable exit codes. The Mora MCP server is optional for read-back and governed memory capture. If the CLI is unavailable, say so up front and STOP; there is no web fallback, and fabricating a brief would be a lie about the user's day.
This is an operator/automation skill, not a read-only briefing skill. It performs configured read-only connector syncs, writes a dated local artifact and log entry, and advances Mora's brief watermark. The pulse-daily scheduler can perform the same advancing effect; the begin gate below safely no-ops when another authorized caller already completed it that day.
The NO-SEND invariant (read first)
This loop NEVER takes an outbound action. It must not email, reply, draft, post, DM, message, create calendar events/tickets, or trigger a notification—even when the brief surfaces something that needs a reply. Configured connectors may make read-only network requests to fetch Gmail, Google Calendar, or GitHub data. The loop must not send vault-derived names, message text, calendar details, or other private context to web, map, recommendation, or unrelated external tools. The selected agent/model may process the rendered brief under its own data policy; this instruction boundary is not a technical sandbox.
The loop's only mutations are Mora-local: the dated brief artifact, watermark, run log, and an optional policy-governed write_memory after explicit user acceptance.
This loop is durable, idempotent, and human-checkpointed: it runs once per logical day, the second run is a no-op, and you advance Mora's state only at explicit gates—never speculatively.
The Flow
Step 1 — Open the loop gate (ALWAYS first)
Run exactly:
mora loop begin daily-brief --json
Branch on the result — do nothing else until you have. Both
already-succeeded and effect-already-committed are exit-10 no-op results;
the latter means the watermark transaction completed but later presentation or
terminal bookkeeping did not:
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.
- 11d ago First seen · 123 lines · 63 tokens per session scan A 91fa0ff375c7
daily-brief-loop is a skill published in the GitHub repository pyranthus-hq/mora (9 stars, last pushed 5d ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,711 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
octo-summary
Read, create, find, and cite Octo summaries through octo-cli. Use when an agent needs to create an owner-only summary from explicit channels, discover summaries visible to its bot owner, inspect one summary, retrieve its current body, or ground an answer in returned citation metadata. Load after octo-shared.
pad
Talk to your project. Natural-language project management — create items, check status, plan work, brainstorm ideas, and more.
onboard
Link this project to a Pad workspace and set it up.
memory-index
Index a folder's contents into the MemPalace semantic memory for search and retrieval. Use this skill whenever the user asks to "index a folder", "index a directory", "index memory", "mine a project into memory", "make a folder searchable", "embed a folder", "ingest code into the palace", or "index this directory for…
memory-mine
Mine project files or conversations into the MemPalace memory system. Indexes source code and conversation history as searchable palace drawers with semantic embeddings and room assignment.
memory-status
Show MemPalace memory system status — drawer counts, wings, rooms, knowledge graph stats, and embedding model state.