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 agents/readycheck-dev/skills/observation-extractorgit clone --depth 1 https://github.com/readycheck-dev/skillsWhat 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.00079 | $0.16841 |
| Opus 5 | $0.00039 | $0.08420 |
| Sonnet 5 | $0.00016 | $0.03368 |
| Haiku 4.5 | $0.00008 | $0.01684 |
Grade A, and why
observation-extractor 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 2d 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 — 1,149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract User Observations
Purpose
Extract user-reported issues from the voice transcript of an ADA capture session. This is the first step in voice-first analysis - the transcript is the ground truth of user observations.
Context
- ADA Binary Directory: {{$ADA_BIN_DIR}}
- Analysis Session Path: {{$ANALYSIS_SESSION_PATH}}
- Capture Session: {{$CAPTURE_SESSION}}
- Output Directory: {{$OUTPUT_DIRECTORY}}
Execution Principles
MUST:
- You MUST process pagination only when the instruction guarded by
<EXTERMELY_IMPORTANT></EXTERMELY_IMPORTANT>appeared in the outputs ofada query {{$CAPTURE_SESSION}} [subcommand]call.
MUST NOT:
- You MUST NOT invent redirect to files when it is not asked to.
- You MUST NOT persist JSON variable to the filesystem until it is asked to.
- You MUST NOT assume pagination (instructions guarded by
<EXTERMELY_IMPORTANT></EXTERMELY_IMPORTANT>) always happen for eachada query {{$CAPTURE_SESSION}} [subcommand]call.
Step 1. Get Session Info and Early Exit Check
Command: ${ADA_BIN_DIR}/ada query {{$CAPTURE_SESSION}} transcribe info --reading-model sonnet --format json --cache-dir {{$ANALYSIS_SESSION_PATH}}/cache
You MUST stop and respond the following JSON immediately if the command fails or word_count is 0.
{"status": "error", "error": "no_voice_recording", "issue_count": 0, "has_ambiguities": false, "fallback_suggestion": "Analyze using screenshots and trace events only"}
Command: ${ADA_BIN_DIR}/ada query {{$CAPTURE_SESSION}} time-info --reading-model sonnet --cache-dir {{$ANALYSIS_SESSION_PATH}}/cache
Set $SESSION_INFO to:
{
"first_event_ns": "[first_event_ns from output]",
"duration_sec": "[duration_sec from output]"
}
You MUST write the contents of $SESSION_INFO (a JSON object) to {{$OUTPUT_DIRECTORY}}/session_info.json.
Read the capture session's platform from its manifest:
Path: ~/.ada/sessions/{{$CAPTURE_SESSION}}/manifest.json
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.
- 2d ago First seen · 1,149 lines · 79 tokens per session scan A 3506dbdf281a
observation-extractor is an agent published in the GitHub repository readycheck-dev/skills (22 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 79 tokens to every session and 16,841 once invoked, about $0.0004 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.