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 agentmods add skills/agno-agi/context/process-todaynpx skills add agno-agi/context --skill process-todaygit clone --depth 1 https://github.com/agno-agi/contextWhat 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 | $0.00069 | $0.00669 |
| Opus 5 | $0.00034 | $0.00334 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 52 lines · 69 tokens per session scan A 20f71419cb97
process-today is a skill published in the GitHub repository agno-agi/context (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 669 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-30.
Other skills, from other repositories
verification
Prove that a coding task is actually complete. Use this after meaningful code changes, when tests/builds fail or are skipped, before marking a plan or goal complete, and whenever acceptance depends on runtime, security, recovery, performance, or cross-module evidence.
repository-investigation
Investigate an unfamiliar repository before changing it. Use this whenever a coding task spans multiple modules, asks for architecture or root-cause analysis, names behavior whose implementation location is unknown, or risks editing before enough evidence is gathered.
safe-refactoring
Execute behavior-preserving or intentionally scoped refactors safely. Use this for multi-file renames, component/service extraction, state-management changes, API migrations, concurrency refactors, or any request where unrelated user work and subtle contracts must be preserved.
wegent-knowledge
Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.
quantmind-dev
Contributor workflow for the QuantMind codebase. Covers contributor setup (environment + hooks), filing issues, commit format, pull request format, and component development across quantmind/ modules (etl, knowledge, configs, preprocess, rag, flows, mind, utils) with tests, examples, and verification. Use when setting…
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.