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/week-plannpx skills add agno-agi/context --skill week-plangit clone --depth 1 https://github.com/agno-agi/contextWrote 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/week-plan)<a href="https://agentmods.dev/skills/agno-agi/context/week-plan"><img src="https://agentmods.dev/badge/skills/agno-agi/context/week-plan.svg" alt="Measured on agentmods" 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 | $0.00070 | $0.00787 |
| Opus 5 | $0.00035 | $0.00394 |
| Sonnet 5 | $0.00014 | $0.00157 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
week-plan 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 4d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Week Plan
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/.
Assemble a clear plan for the next 7 days from the structured crm
store, enriched from the connected sources. This is a read-only retrieval
workflow: it pulls, merges, and formats — it never writes anything.
Procedure
- Anchor on now. Use the current datetime already in your context. The
window is
now→now + 7 days. - Pull the two time-bearing tables with
query_crm(one retrieval — ask it for both):- Meetings whose
starts_atfalls between now and now + 7 days. - Reminders with
status = 'pending'anddue_at≤ now + 7 days. Include anything already overdue (due_at < now, still pending) — a plan that hides what's late isn't useful.
- Meetings whose
- If the
calendarsource is connected, pull the real calendar too —query_calendarfor events in the same 7-day window — and merge with the CRM meetings (dedupe by title + start time; the calendar wins on times). - Enrich from connected sources. When the
slacksource is connected,query_slackfor recent threads that touch this week's meetings, attendees, or active projects — surface commitments and deadlines that never made it into the CRM as plan items, flagged(from slack). When a meeting or reminder ties to a project with a brief in the knowledge base, pull its status fromquery_knowledgeso the plan reflects where things actually stand. Enrichment is bounded: it adds context to the week's items, it doesn't grow the window. - Order meetings and reminders by their time column, ascending.
Format
- Lead with an Overdue section only if past-due pending reminders exist; note how late each one is.
- Then one heading per day (today through day 7), in date order. Under each day list its meetings (with start time) and any reminders due that day.
- Skip days with nothing — don't pad the plan with empty dates.
- Close with a one-line tally, e.g.
3 meetings, 5 reminders, 1 overdue.
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.
- 4d ago First seen · 59 lines · 70 tokens per session scan A dfde1f4e7598
week-plan is a skill published in the GitHub repository agno-agi/context (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 787 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…
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.