Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/agno-agi/contextnpx agentmods add skills/agno-agi/context/process-todayWrote 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/agno-agi/context/process-today)<a href="https://agentmods.dev/skills/agno-agi/context/process-today"><img src="https://agentmods.dev/badge/skills/agno-agi/context/process-today/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/agno-agi/context/process-today"><img src="https://agentmods.dev/badge/skills/agno-agi/context/process-today.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.00069 | $0.00669 |
| Opus 5.5 | $0.00028 | $0.00268 |
| Sonnet 5.5 | $0.00014 | $0.00134 |
| Haiku 4.5 | $0.00007 | $0.00067 |
Grade A, and why
process-today 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 1mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process Today
Runtime skill — a playbook the deployed @context agent runs for its owner, invoked in natural language. Not a coding-agent workflow; those live in
.agents/skills/.
Turn today's raw activity into filed context. Unlike the read-only playbooks,
this one writes — it ends in update_crm / update_knowledge calls, not
just a summary. It still never acts on the outside world: no mail, no calendar
changes, nothing leaves.
Procedure
- Anchor on now. "Today" is the start of the local day → now.
- Gather the day's raw material:
rundown— inbound updates from others. (It marks what it shows as briefed; do not acknowledge anything — that's the owner's call.)query_crm— today's meetings and the reminders that came due today.- When connected:
query_calendarfor today's events;query_slackfor today's threads the owner took part in;query_gmailfor today's meaningful exchanges.
- Extract what has lasting value. From that material, pick out:
- a new person → contact
- a thing that happened, a decision made in a thread → note
- a commitment with a date ("I'll send it Friday") → reminder with
due_at - a follow-up that got scheduled → meeting
- durable prose (a decision on a spec, how something now works) → the knowledge base, in the right spec sub-file Skip chit-chat, scheduling back-and-forth, and anything already on file.
- File it with
update_crm/update_knowledge, deduping against what exists (an existing contact gets updated, not duplicated). Writes are additive — never flip reminder or ack status and never delete anything in this playbook. - Report the digest. One line per item filed (what + where), then a short "left unfiled" line for material judged not worth keeping, so the owner can overrule.
Edge cases
- Safe unattended. Scheduled runs work end to end: this playbook reads and files but never sends, so no approval gate fires.
- A quiet day is a one-line report ("Nothing worth filing today.") — not an invented summary.
- When unsure whether something is durable, file a note — cheap to ignore later, expensive to lose.
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.
- 1mo ago First seen · 52 lines · 69 tokens per session scan A 20f71419cb97
process-today is a skill published in the GitHub repository agno-agi/context (13 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 669 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
gsd-ns-manage
config workspace | workstreams thread update ship inbox.
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…
triage-inbox
Triage academic email and calendar (Gmail / Google Calendar via the session's MCP) into a prioritized digest plus a referee-obligations tracker — classifying referee requests, R&R and editor correspondence, co-author threads, seminar and conference invites, and grant/admin deadlines, and proposing a human-gated action…
cs-escalation-brief
Redacta un informe de escalada estructurado para una cuenta de cliente en riesgo. Úsalo cuando una cuenta haya escalado, cuando un cliente amenace con cancelar, cuando un problema de cliente P1 requiera atención ejecutiva, o cuando prepares un plan de retención interno. Produce un informe de escalada preciso con…
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.