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 nullhack/temple8 --skill research-providergit clone --depth 1 https://github.com/nullhack/temple8Wrote 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/nullhack/temple8/research-provider)<a href="https://agentmods.dev/skills/nullhack/temple8/research-provider"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/research-provider/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/nullhack/temple8/research-provider"><img src="https://agentmods.dev/badge/skills/nullhack/temple8/research-provider.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.00031 | $0.00348 |
| Opus 5.5 | $0.00012 | $0.00139 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
research-provider 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 1mo 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
Research Provider
- Load [[software-craft/external-fixtures]] — the kind-dispatch table (docs-focus, recorder, scrub-fields, default specialist).
- Identify the exact provider — the specific service and version, not just its kind.
- Research online: websearch the provider and webfetch its official docs. Read for reference, authentication/credentials scheme, client/SDK, error catalog, rate limits, pagination, idempotency, known gotchas. Do not write probe code until the docs are read.
- Determine the access shape: endpoint base/URI, protocol, credentials source (a named variable the user must supply in
~/.secrets/<project>.env), request/response shape, and both success and failure modes. Per [[software-craft/secrets-and-config]] the agent names the variable and instructs the user where to set it; it never holds or prints the value. - Recommend at most one advisory specialist for this provider. IF the provider raises auth/secrets/PII concerns THEN recommend security; IF schema/message-shape THEN data; IF user-facing flows THEN ux; IF project-specific semantics THEN domain.
- Dispatch on the service kind (HTTP API, external database, message queue/event stream, object storage, other) for the docs-focus and default-specialist per [[software-craft/external-fixtures]] — the kind table is the one knob that varies.
- IF the docs reveal the service behaves differently than the interview assumed THEN signal a mismatch.
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.
- 1mo ago First seen · 15 lines · 31 tokens per session scan A 75ae3338e308
research-provider is a skill published in the GitHub repository nullhack/temple8 (11 stars, last pushed 29d ago), licensed MIT. It adds 31 tokens to every session and 348 once invoked, about $0.0001 per session on Opus 5.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
agentic-test-audit
Audit a pytest suite: surviving mutants and untested code, flaky, order-dependent and slow tests, and removal candidates checked on held-out mutants. Report-only.
agentic-verify
Check that a Python change is caught by tests: run every mutant of the changed lines and write tests until they catch them. Reports evidence instead of a diff to read.
test-generator
Generate pytest test cases for Python functions and classes.
python
Use when the task is Python itself, in any framework or none: PEP 695 generics, mypy --strict typing, dataclass/Protocol/TypedDict/Enum choices, asyncio.TaskGroup, stdlib idioms, src/ layout + pyproject.toml with uv, ruff+mypy+pytest gate. NOT a FastAPI/ASGI service (that is fastapi), NOT a deep pytest suite (that is…
clawrium-release-announcements
Daily — draft a release blog post, open a PR, iterate on comments until merged.
blog-author
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.