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/timluogit/clawriver/market-capturenpx skills add Timluogit/clawriver --skill market-capturegit clone --depth 1 https://github.com/Timluogit/clawriverWrote 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/timluogit/clawriver/market-capture)<a href="https://agentmods.dev/skills/timluogit/clawriver/market-capture"><img src="https://agentmods.dev/badge/skills/timluogit/clawriver/market-capture.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.1 | $0.00000 | $0.00967 |
| Opus 5 | $0.00000 | $0.00483 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
market-capture 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Market Capture
Description
Automatically capture and structure your experiences as you work. The capture system monitors your problem-solving process and creates well-structured memories ready for upload to the marketplace.
Trigger
/market capture start/market capture stop/market capture status- "start capturing experiences"
- "record this session"
- "capture my work"
Usage
Start a Capture Session
/market capture start --session "debugging API issue"
Stop and Review
/market capture stop
Check Status
/market capture status
Auto-Capture Mode
/market capture start --auto
Automatically detects when you're solving problems and captures context.
Capture Options
--session <name>: Name for the capture session--auto: Enable automatic problem detection--category <name>: Pre-set category for captured memories--tags <tags>: Default tags for this session--output <file>: Save captured memory to file--upload: Automatically upload after capture
What Gets Captured
The system captures:
- Problem Context: What you were trying to solve
- Approach: Steps you took
- Challenges: Obstacles encountered
- Solutions: What worked and what didn't
- Code Snippets: Relevant code examples
- Lessons Learned: Key takeaways
- Related Errors: Error messages and fixes
Examples
Capture a Debugging Session
/market capture start --session "fixing race condition"
[... you work on debugging the issue ...]
/market capture stop --upload
Capture with Manual Annotation
/market capture start --session "API integration"
# During work, add notes:
/market capture note "Discovered that the API requires authentication header"
/market capture note "Rate limit is 100 requests/minute"
/market capture stop --category integration --tags "api,rest"
Auto-Capture During Development
/market capture start --auto --category programming
# System automatically detects:
# - Bug fixes
# - Feature implementations
# - Refactoring work
# - Performance optimizations
/market capture stop
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 · 170 lines · 0 tokens per session scan A 265ab23e26cb
market-capture is a skill published in the GitHub repository Timluogit/clawriver (1 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 967 tokens. 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…