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/nullhack/temple8/research-providernpx skills add nullhack/temple8 --skill research-providergit clone --depth 1 https://github.com/nullhack/temple8What 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.00031 | $0.00348 |
| Opus 5 | $0.00015 | $0.00174 |
| Sonnet 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 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.
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.
- 2d 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 27d ago), licensed MIT. It adds 31 tokens to every session and 348 once invoked, about $0.0002 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 skills, from other repositories
load-github-action-thread
Download retained Codex GitHub Action thread artifacts and load their rollout history into the local Codex app. Use when asked to open, load, import, resume, or inspect a Codex automation thread from a GitHub Actions run or a related GitHub issue or pull request.
test-generator
Generate pytest test cases for Python functions and classes.
python-binance
Help developers use the python-binance library for trading on Binance. Use when code imports binance, references Client/AsyncClient, or asks about Binance API trading, market data, websockets, or account management.
itx:execute
Execute the plan for an issue (parent or subtask).
clawctl
Know the clawctl CLI and manage your Clawrium fleet (hosts, agents, providers, channels, integrations, skills, secrets).
create-playwright
Record a browser-session demo (MP4) using Playwright via a replay-first compile pipeline. A YAML spec drives the driver script, the recording, and the ElevenLabs voiceover — mirrors create-vhs for browser flows.