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/stoa-platform/stoa/competitive-watchnpx skills add stoa-platform/stoa --skill competitive-watchgit clone --depth 1 https://github.com/stoa-platform/stoaWrote 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/stoa-platform/stoa/competitive-watch)<a href="https://agentmods.dev/skills/stoa-platform/stoa/competitive-watch"><img src="https://agentmods.dev/badge/skills/stoa-platform/stoa/competitive-watch.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.00018 | $0.01362 |
| Opus 5 | $0.00009 | $0.00681 |
| Sonnet 5 | $0.00004 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
competitive-watch 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 5d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competitive Watch Skill
Veille concurrentielle integree a l'IA Factory STOA. 3 niveaux d'execution.
Sources (par priorite)
1. Boris Cherny (@bcherny) — Createur Claude Code
- X/Twitter : https://x.com/bcherny
- Threads : https://threads.net/@boris_cherny
- Agregateur : https://howborisusesclaudecode.com
- Frequence : ~1 thread majeur / 2 semaines
2. Anthropic Engineering Blog
- https://www.anthropic.com/engineering
- https://www.anthropic.com/news
- Claude Code changelog :
claude --version+ release notes
3. Claude Code Docs & Releases
- https://code.claude.com/docs
- https://github.com/anthropics/claude-code/releases
- Version check :
npm view @anthropic-ai/claude-code version
4. Concurrence directe
| Outil | Changelog | Focus |
|---|---|---|
| Cursor | https://cursor.com/changelog | Composer, multi-file, AI rules |
| Windsurf (Codeium) | https://codeium.com/blog | Cascade, flows |
| Aider | https://aider.chat/HISTORY.html | Modes, benchmarks |
| OpenAI Codex CLI | https://github.com/openai/codex | Sandbox, autonomie |
| Amazon Q Developer | https://aws.amazon.com/q/developer/ | AWS integration |
| Google Jules / Gemini CLI | https://developers.googleblog.com | Workspace integration |
5. Communaute
- Reddit r/ClaudeAI : top posts semaine
- Reddit r/cursor : top posts semaine
- Hacker News : recherche "Claude Code" ou "AI coding"
- Dev.to / Medium : tags "claude-code", "ai-coding-assistant"
6. MCP Ecosystem
- https://github.com/modelcontextprotocol
- Nouveaux MCP servers populaires
- Patterns d'integration emergents
Architecture L1 — Mode Accumulation
L1 fonctionne en 2 phases (collect + digest) avec accumulation JSONL:
watch-collect.sh (2x/jour) watch-digest.sh (lundi)
Sources → JSONL append → Dedup + tri + format digest
.claude/watch/signals-YYYY-WNN.jsonl
Phase 1: Collect (watch-collect.sh)
- Cadence: 2x/jour (08:00 + 18:00 CET)
- Append-only: chaque signal = 1 ligne JSONL
- Dedup a l'ecriture: source+title (case-insensitive)
- Fichier par semaine ISO:
signals-2026-W09.jsonl - 6 sources: Anthropic blog, npm, Reddit, HN, Cursor, Aider
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.
- 5d ago First seen · 138 lines · 18 tokens per session scan A f9ff5d7f4d2b
competitive-watch is a skill published in the GitHub repository stoa-platform/stoa (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,362 once invoked, about $0.0001 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-31.
Other skills, from other repositories
lyrik
Security assessment of a codebase — minimal mode for runner validation.
librarian
Read-only retrieval over the daily-digest kept set. Slash-invoke with /librarian ; returns items verbatim with citations.
notes
Create and manage text notes in the workspace.
tdx-assets
Look up staff devices, assets, and locations in TeamDynamix (TDX). Given a list of names, emails, or partial identifiers, resolve each person and return the assets assigned to them with location, model, ownership type, and status. Read-only.
aggregator
Daily fetch from a fixed public allowlist; score against the user's interests file; cluster into themes; push the digest to the configured channel.
github
GitHub operations via the gh CLI.