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 nota-america/forgecat-agent-profiles --skill digestgit clone --depth 1 https://github.com/nota-america/forgecat-agent-profilesWrote 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/nota-america/forgecat-agent-profiles/digest)<a href="https://agentmods.dev/skills/nota-america/forgecat-agent-profiles/digest"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/digest/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/nota-america/forgecat-agent-profiles/digest"><img src="https://agentmods.dev/badge/skills/nota-america/forgecat-agent-profiles/digest.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.00048 | $0.01313 |
| Opus 5 | $0.00024 | $0.00656 |
| Sonnet 5 | $0.00010 | $0.00263 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
digest 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 8d 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.
This is a copy
100% identical to digest — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Digest Command
If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (
.forgecat/profiles/@forgecat/anthropics_knowledge-work-plugins_enterprise-search/CONNECTORS.md).
Scan recent activity across all connected sources and generate a structured digest highlighting what matters.
Instructions
1. Parse Flags
Determine the time window from the user's input:
--daily— Last 24 hours (default if no flag specified)--weekly— Last 7 days
The user may also specify a custom range:
--since yesterday--since Monday--since 2025-01-20
2. Check Available Sources
Identify which MCP sources are connected (same approach as the search command):
- ~~chat — channels, DMs, mentions
- ~~email — inbox, sent, threads
- ~~cloud storage — recently modified docs shared with user
- ~~project tracker — tasks assigned, completed, commented on
- ~~CRM — opportunity updates, account activity
- ~~knowledge base — recently updated wiki pages
If no sources are connected, guide the user:
To generate a digest, you'll need at least one source connected.
Check your MCP settings to add ~~chat, ~~email, ~~cloud storage, or other tools.
3. Gather Activity from Each Source
~~chat:
- Search for messages mentioning the user (
to:me) - Check channels the user is in for recent activity
- Look for threads the user participated in
- Identify new messages in key channels
~~email:
- Search recent inbox messages
- Identify threads with new replies
- Flag emails with action items or questions directed at the user
~~cloud storage:
- Find documents recently modified or shared with the user
- Note new comments on docs the user owns or collaborates on
~~project tracker:
- Tasks assigned to the user (new or updated)
- Tasks completed by others that the user follows
- Comments on tasks the user is involved with
~~CRM:
- Opportunity stage changes
- New activities logged on accounts the user owns
- Updated contacts or accounts
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.
- 8d ago First seen · 177 lines · 48 tokens per session scan A 812269874210
digest is a skill published in the GitHub repository nota-america/forgecat-agent-profiles (66 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 1,313 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to digest, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
ceo-setup
One-time onboarding for the executive/manager commitment workflow — delegation-heavy, meeting prep, decision capture, morning and evening digests. Creates a commitments project and installs two dashboard widgets. After successful setup this skill is excluded from selection until the marker file is deleted.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
openase-platform
Platform operations for tickets, projects, and runtime coordination inside OpenASE.
team-culture
Help users design and maintain a high-performing culture by balancing radical transparency, psychological safety, and a relentless focus on customer delight.
feishu-interaction
Feishu/Lark platform interaction via MCP - documents, tasks, calendar, Bitable, messaging.