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.
git clone --depth 1 https://github.com/yempik-ai/cowork-osWrote 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/commands/yempik-ai/cowork-os/weekly-pulse)<a href="https://agentmods.dev/commands/yempik-ai/cowork-os/weekly-pulse"><img src="https://agentmods.dev/badge/commands/yempik-ai/cowork-os/weekly-pulse/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/commands/yempik-ai/cowork-os/weekly-pulse"><img src="https://agentmods.dev/badge/commands/yempik-ai/cowork-os/weekly-pulse.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.00033 | $0.00263 |
| Opus 5 | $0.00016 | $0.00131 |
| Sonnet 5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
weekly-pulse 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.
What it actually says
/cowork-os:weekly-pulse
Produce a short weekly marketing pulse: a Monday brief on what marketing did and the week's priorities.
- Read
marketing/strategy.md,marketing/campaigns.md,marketing/content.md, and the latest file inreviews/if present. - If analytics or ads connectors are connected, pull the key numbers for the last 7 days. If not, say so and work from the workspace memory. Never invent numbers.
- Output three blocks: (a) what happened last week, facts only; (b) what it means, 2-3 reads; (c) the 3 highest-impact priorities for this week, each with a concrete next action and an owner.
- Keep it short and scannable. Separate facts, assumptions, and recommendations.
End with a Memory Update (file the brief in reviews/, route new insight to marketing/strategy.md).
This is meant to run on a schedule (suggested cadence: Monday 08:00). Offer to set it up as a scheduled task.
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 · 17 lines · 33 tokens per session scan A 26f0faa3ac7d
weekly-pulse is a command published in the GitHub repository yempik-ai/cowork-os (70 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 263 once invoked, about $0.0002 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 commands, from other repositories
reflect
Reflect on recent work — log lessons to the journal and propose distilled rule updates for review.
doctor
Check vault health — broken links, orphans, missing frontmatter, MISSING placeholders — and propose fixes.
analyze
Analyze Claude Code transcripts to surface subagent behavior and improvement opportunities.
react-router-client-loader
Do this in a clientLoader and use loaderData to render the component. DO NOT create mock data, new interfaces, or mock data loader functions. Instead, assume loaderData has all of the data you need to render the component.
sol
Run a one-shot task on the routed Codex model (gpt-5.6-sol by default) and relay its answer.
pseo-gbp-audit
Use when: kullanıcı "GBP audit", "Google Business Profile kontrol", "placeid eksik mi", "business listing kontrol", "harita listing audit", "google haritalar profili", "GMB audit", "local listing gap" der ya da /pseo-gbp-audit çağırırsa. Also use when: aktif projenin project.config.profiles array'inde "local-service"…