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/resciencelab/opc-skills/templatenpx skills add ReScienceLab/opc-skills --skill templategit clone --depth 1 https://github.com/ReScienceLab/opc-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/skills/resciencelab/opc-skills/template)<a href="https://agentmods.dev/skills/resciencelab/opc-skills/template"><img src="https://agentmods.dev/badge/skills/resciencelab/opc-skills/template.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 | $0.00039 | $0.00652 |
| Opus 5 | $0.00019 | $0.00326 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
skill-name 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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Name
Brief description of the skill and its purpose.
Prerequisites
List any setup requirements:
- Environment variables needed
- API keys required
- Dependencies (already listed in frontmatter above)
Example setup:
export SKILL_API_KEY="your_api_key"
Quick Start
How to use the skill quickly:
cd <skill_directory>
python3 scripts/command.py --option value
Usage Examples
Example 1: Basic usage
python3 scripts/script.py "input"
Output:
Expected output here
Example 2: Advanced usage
python3 scripts/script.py "input" --flag --option value
Commands
All commands run from the skill directory.
Command 1
python3 scripts/script1.py --help
python3 scripts/script1.py "param1" --option value
Command 2
python3 scripts/script2.py "param1" "param2"
Scripts
script1.py- Description of what this script doesscript2.py- Description of what this script does
API Info
- Base URL: (if applicable)
- Rate Limits: (if applicable)
- Auth: (how authentication works)
- Docs: Link to official documentation
Troubleshooting
Issue 1
Symptom: Description of the problem
Solution:
- Step 1
- Step 2
Issue 2
Symptom: Description of the problem
Solution:
- Step 1
- Step 2
Examples
See examples/ directory for full workflow examples.
References
Notes
- Important note 1
- Important note 2
Frontmatter Guide
The YAML frontmatter at the top of this file is required:
| Field | Type | Required | Description |
|---|---|---|---|
name |
string | ✓ | Unique identifier (kebab-case) |
description |
string | ✓ | What the skill does and when to use it. Include trigger keywords and "Use when..." contexts inline. |
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.
- 4d ago First seen · 130 lines · 39 tokens per session scan A afb58b6609bc
skill-name is a skill published in the GitHub repository ReScienceLab/opc-skills (1,754 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 652 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
context-okf-llm-ingest
Use when extracting a codebase's implementation decisions into Metatron with an LLM/agent instead of metatron ingest — authoring candidate decisions as Open Knowledge Format (OKF) markdown files locally for review.
context-okf-promote-candidates
Use when promoting reviewed Metatron candidate decisions to canonical in a git/CI flow — moving Open Knowledge Format (OKF) files from candidate/ to decisions/. The agent performs only human-named moves; it never decides what to promote.
live-audit
Audit steam-games-mcp — build/test/lint gate, live MCP tool edge-case sweep (input validation, SteamID64/vanity/appid edge cases, key-gating), and source-level code review. Use when asked to test/audit the published or just-fixed steam-games-mcp package, hunt for bugs/edge cases, or repeat "the same kind of testing as…
live-audit
Repo-specific playbook, for any agent/model working on this repo (not tied to a particular harness — see AGENTS.md's own framing). Use it when asked to test/audit/smoke-test the published tmdb-mcp package, hunt for bugs or edge cases, or repeat "the same kind of testing as before.".
prompt-check
Live-test every MCP Prompt in src/tools/prompts.ts through the real MCP protocol (not a static read) across every argument combination. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.
prompt-check
Live-test every MCP Prompt in src/prompts.ts through the real MCP protocol (not a static read) across every argument combination, including every enum value. Use when a prompt is added or its argument-handling logic changes, or as part of a live-audit pass.