Borrowing it
Nothing to install: this file belongs to pillaiharish/opencode-ollama-steroids. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/pillaiharish/opencode-ollama-steroids/main/.opencode/skills/opencode-ollama-agent-guardrails/SKILL.mdgit clone --depth 1 https://github.com/pillaiharish/opencode-ollama-steroidsWrote 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/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails)<a href="https://agentmods.dev/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails/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/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails.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.00047 | $0.00398 |
| Opus 5.5 | $0.00019 | $0.00159 |
| Sonnet 5.5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
opencode-ollama-agent-guardrails 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 2mo 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
OpenCode Ollama Agent Guardrails
Use this skill when configuring, running, reviewing, or publishing an OpenCode + Ollama multi-agent coding workflow.
Required Agent Split
Builder agent:
- plans the current task;
- implements only approved scope;
- runs validation;
- writes implementation notes and test results;
- fixes blocking issues inside scope;
- stops for human review and commit approval.
Reviewer agent:
- reviews builder plans, diffs, tests, generated output, screenshots, and security posture;
- blocks scope creep and weak tests;
- writes only review and signoff files under the current session folder;
- never edits product code.
Hard Rules
- Do not commit, push, rebase, force-push, or start another prompt.
- Do not publish raw prompts, raw OpenCode logs, session exports, or private screenshots.
- Do not use local absolute paths in public-bound files.
- Do not claim success unless the required validation commands passed.
- Do not weaken tests to pass.
- Do not let reviewers edit production code.
- Do not let agents edit resolver-owned prompt model locks ending in
_MODELS.json. - Stop after final signoff so a human can inspect and decide whether to commit.
Session Rules
Use:
agent-sessions/<project-slug>/<prompt-id>/
Product edits belong only under the configured product repo, usually:
product-repo/
Raw logs may stay local in the session folder, but they must remain ignored.
Decision Vocabulary
Reviewer decisions must be exactly one of:
APPROVEDCHANGES_REQUESTEDSIGNED_OFFNOT_SIGNED_OFF
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.
- 2mo ago First seen · 63 lines · 47 tokens per session scan A 70acdcd169d7
opencode-ollama-agent-guardrails is a skill published in the GitHub repository pillaiharish/opencode-ollama-steroids (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 398 once invoked, about $0.0002 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-31.
Other skills, from other repositories
audit-artifact
Interactive workflow for auditing a SpecRoute artifact before it is treated as implementation-ready. Use when checking a PRD, spec triplet, prompt set, agent file, skill, command, hook, rule, or runtime layout. Asks which artifact path to inspect and which contract to apply. Triggers - "audit this artifact", "check…
review
Use when a green diff needs adversarial judgment in the rsc SDD chain, between verify and ship — give a review keyed to the spec/plan/constitution in 02-DOCS/wiki/sdd/, or receive one and verify each comment before agreeing. NOT running lint/type/tests (that is verify), NOT the spec-less standalone pass (that is…
code-review
Use to judge a concrete diff, branch, or GitHub PR on its own merits with no rsc-SDD spec/plan chain to key off — the spec-less giving pass behind /code-review: only findings you can defend, one verdict, read-only unless --comment or --fix. NOT the SDD gate keyed to 02-DOCS/wiki/sdd/ that also processes incoming…
review-this-branch
Run the nohuman review gate (fresh-session adversarial reviewer + tamper guard) over the current branch or a GitHub pull request, with no server, no database, and no onboarding, and relay the pass/fail checklist.
ollama
Use when running open-weight LLMs locally with Ollama — pulling and tagging models, calling the local API, picking a quantization or GGUF, writing Modelfiles, and sizing VRAM and RAM for the machine at hand. NOT remote or managed GPU serving and autoscaling (that is runpod), NOT downloading raw weights or datasets…
receiving-code-review
Processes review feedback until the change is approved.