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/simple10/agents-observe/observenpx skills add simple10/agents-observe --skill observegit clone --depth 1 https://github.com/simple10/agents-observeWrote 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/simple10/agents-observe/observe)<a href="https://agentmods.dev/skills/simple10/agents-observe/observe"><img src="https://agentmods.dev/badge/skills/simple10/agents-observe/observe.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.00008 | $0.01314 |
| Opus 5 | $0.00004 | $0.00657 |
| Sonnet 5 | $0.00002 | $0.00263 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade A, and why
observe 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/observe
Agents Observe dashboard and server management.
Usage
/observe view— Open the current session in the dashboard/observe stats— Open the current session's stats modal in the dashboard/observe— Open the dashboard URL/observe status— Show server health and config details/observe start— Start the server/observe stop— Stop the server/observe restart— Restart the server/observe logs-server— Show recent Docker container logs/observe logs-cli— Tail the local cli.log file/observe logs-mcp— Tail the local mcp.log file/observe debug— Diagnose server issues (health, docker logs, mcp.log, cli.log)
Instructions
All commands are invoked via the wrapper at scripts/cli.sh, which resolves the path to observe_cli.mjs relative to this skill's install location. Do not reach outside the skill dir with ../ paths — the agentskills spec disallows it and it breaks portability across agents.
The subcommand is in $ARGUMENTS. If empty, default to showing the dashboard URL.
/observe view
Opens the current session in the dashboard.
- Run health to get the dashboard origin:
scripts/cli.sh health - From the output, take the
Dashboard:URL (e.g.http://localhost:4981). If exit code 1, the server isn't running — tell the user to run/observe startand stop here. - Construct the session URL:
<dashboard>/#/_/${CLAUDE_SESSION_ID}(the_is the project placeholder; the dashboard resolves the real project from the session id). - Open it in the user's default browser using the platform-appropriate command —
open <url>on macOS,xdg-open <url>on Linux,start <url>on Windows. Pick based on thePlatform:line in your environment context. - Also print the URL in your response so the user can re-open it if needed.
/observe stats
Opens the current session's stats modal in the dashboard, using a deep-link URL.
- Run health to get the dashboard origin:
scripts/cli.sh health - From the output, take the
Dashboard:URL (e.g.http://localhost:4981). If exit code 1, the server isn't running — tell the user to run/observe startand stop here. - Construct the deep link:
<dashboard>/#/_/${CLAUDE_SESSION_ID}:session.stats - Open it in the user's default browser using the platform-appropriate command —
open <url>on macOS,xdg-open <url>on Linux,start <url>on Windows. Pick based on thePlatform:line in your environment context. - Also print the URL in your response so the user can re-open it if needed.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 155 lines · 8 tokens per session scan A 2e2ff0d4f0bd
observe is a skill published in the GitHub repository simple10/agents-observe (666 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 1,314 once invoked, about $0.0000 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…