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 EliBarak12/Elliot --skill observe-agent-runsgit clone --depth 1 https://github.com/EliBarak12/ElliotWrote 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/elibarak12/elliot/observe-agent-runs)<a href="https://agentmods.dev/skills/elibarak12/elliot/observe-agent-runs"><img src="https://agentmods.dev/badge/skills/elibarak12/elliot/observe-agent-runs/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/elibarak12/elliot/observe-agent-runs"><img src="https://agentmods.dev/badge/skills/elibarak12/elliot/observe-agent-runs.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.00049 | $0.00887 |
| Opus 5 | $0.00024 | $0.00443 |
| Sonnet 5 | $0.00010 | $0.00177 |
| Haiku 4.5 | $0.00005 | $0.00089 |
Grade B, and why
observe-agent-runs scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`~/.claude/settings.json` for Claude Code), returns the config path it How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observe Agent Runs
You are wiring the Elliot trace hook into a coding agent's config so the full session — prompt, model reasoning, tool calls, and final answer — appears in the Agent Console. Without the hook the Console only sees MCP tool calls, which is half the story: the why lives in the prompt and the reasoning.
This is principle #4 — every agent session is observable — operationalised.
Prerequisite
Elliot must be running (make dev). The hook posts to the connector-runtime
at http://localhost:3001/v1/trace/ingest, so the runtime port (3001) needs
to be reachable from the agent's machine. If the user runs Elliot on a remote
host, set ELLIOT_RUNTIME_URL in their shell before installing.
Steps
1. Check current state
Call elliot_trace_hook_status. It returns the runtime URL the hook will
post to and, for each supported harness (claude-code, codex, cursor),
whether it's installed today and the config path it lives in.
If the harness the user uses already shows installed: true, jump to step 3
and tell them what they'd see when they next run that harness.
2. Install for the right harness
Ask the user which agent they want streamed into Elliot (or detect from
context — if they're talking to you in Claude Code, default to claude-code).
Call elliot_install_trace_hook(harness="<harness>") with one of:
claude-code, codex, cursor.
It writes a hook entry into the harness config (e.g.
~/.claude/settings.json for Claude Code), returns the config path it
touched, and the runtime URL the hook will post to. Tell the user:
"Installed the trace hook into
<config_path>. Restart<harness>; its next prompts, reasoning, tool calls, and final answers will stream into the Agent Console at http://localhost:5173/agents."
3. Verify it works
After the user restarts the harness and makes one call, ask them to refresh the Agent Console. They should see a new run entry that includes the prompt text and the model's reasoning, not just the tool calls.
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 · 81 lines · 49 tokens per session scan B 9fa002dfd6e6
observe-agent-runs is a skill published in the GitHub repository EliBarak12/Elliot (11 stars, last pushed 10d ago), licensed MIT. It adds 49 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-workflow-automation
Agent skill for workflow-automation - invoke with $agent-workflow-automation.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-trading-predictor
Agent skill for trading-predictor - invoke with $agent-trading-predictor.
agent-pseudocode
Agent skill for pseudocode - invoke with $agent-pseudocode.