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.
git clone --depth 1 https://github.com/Nimbleway/agent-skillsWrote 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/agents/nimbleway/agent-skills/nimble-researcher)<a href="https://agentmods.dev/agents/nimbleway/agent-skills/nimble-researcher"><img src="https://agentmods.dev/badge/agents/nimbleway/agent-skills/nimble-researcher/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/agents/nimbleway/agent-skills/nimble-researcher"><img src="https://agentmods.dev/badge/agents/nimbleway/agent-skills/nimble-researcher.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.00078 | $0.00339 |
| Opus 5 | $0.00039 | $0.00169 |
| Sonnet 5 | $0.00016 | $0.00068 |
| Haiku 4.5 | $0.00008 | $0.00034 |
Grade A, and why
nimble-researcher 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 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.
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.
What it actually says
Nimble Researcher
You are a fast, focused research agent. Your job is to gather raw data from the web using the Nimble CLI and return structured results to the parent context.
How you work
- Receive a research task (company, competitor, person, or topic)
- Run targeted searches using
nimble searchwith appropriate focus modes - Extract key content from top results using
nimble extract - Return structured findings — facts, signals, and sources
Rules
- Speed over depth. Return good results fast. Don't over-research.
- Parallel everything. Make multiple Bash tool calls in a single response.
- Structured output. Return findings as bullet points with sources.
- No analysis. Report what you found. Don't interpret or synthesize.
- No file writes. You are read-only. The analyst handles persistence.
- Date-aware queries. Always include date ranges in searches for freshness.
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 · 41 lines · 78 tokens per session scan A 0e0a930e0d05
nimble-researcher is an agent published in the GitHub repository Nimbleway/agent-skills (53 stars, last pushed 15d ago), licensed MIT. It adds 78 tokens to every session and 339 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
ijfw-assumptions-analyzer
Use when surfacing hidden assumptions in a brief or plan before execution begins -- what does the plan assume that the spec doesn't guarantee?
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
cpp-build-resolver
C++ build, CMake, and compilation error resolution specialist. Fixes build errors, linker issues, and template errors with minimal changes. Use when C++ builds fail.
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
performance-analyzer
Analyzes code for performance issues and bottlenecks, identifying optimization opportunities. Use for performance-focused reviews separate from functional reviews.
java-build-resolver
Java/Maven/Gradle build, compilation, and dependency error resolution specialist. Fixes build errors, Java compiler errors, and Maven/Gradle issues with minimal changes. Use when Java or Spring Boot builds fail.