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 romarayt/raytsystem-public-os --skill raytsystem-security-reviewgit clone --depth 1 https://github.com/romarayt/raytsystem-public-osWrote 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/romarayt/raytsystem-public-os/raytsystem-security-review)<a href="https://agentmods.dev/skills/romarayt/raytsystem-public-os/raytsystem-security-review"><img src="https://agentmods.dev/badge/skills/romarayt/raytsystem-public-os/raytsystem-security-review/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/romarayt/raytsystem-public-os/raytsystem-security-review"><img src="https://agentmods.dev/badge/skills/romarayt/raytsystem-public-os/raytsystem-security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00069 | $0.00465 |
| Opus 5.5 | $0.00028 | $0.00186 |
| Sonnet 5.5 | $0.00014 | $0.00093 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
raytsystem-security-review 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
raytsystem Security Review
Inputs and outputs
- Accept one bounded change/run plus threat model and declared permissions.
- Return confirmed or unproven Critical/High findings with repro, violated invariant, and minimal regression test/fix.
Write scope
- Keep review read-only; run only non-mutating diagnostics or isolated synthetic tests.
- Never read secrets without scoped necessity, disclose values, promote, publish, or modify external systems.
Preflight
- Run
uv run raytsystem agent preflight --skill raytsystem-security-review --write --jsonlocally. - Run
agent subagent-checkbefore delegation; hosted review receives only safe excerpts. - Snapshot declared canonical/external state and identify every write/egress boundary.
Workflow
- Trace untrusted input through Fetcher/Extractor/proposal/validation/promotion/query/save paths.
- Test raw/hash/citation closure, generation races, lease fencing, WAL/pointer crash windows, and idempotency.
- Test SQL/FTS injection, resource limits, archive/parser containment, symlink/hardlink/no-follow paths, and secret redaction.
- Verify zero unapproved process/network/outbox/Git/external action.
Validation
- Require a regression test for every confirmed Critical/High issue.
- Re-run scoped and full gates after fixes; never accept skipped required tests.
- Exercise evals
m3-security-review-goldenandm3-security-review-adversarial.
Recovery
- Preserve failed staging and machine-readable reports; retry only classified transient failures.
- On quota/tool loss, list exact reviewed surfaces and remaining adversarial cases.
Stop and approval conditions
- Stop on secret/PII exposure, unsafe external destination, real promotion, destructive action, or missing authority.
- Do not downgrade a confirmed issue because exploitation is inconvenient; fail closed and request the narrow required approval.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 46 lines · 69 tokens per session scan A 3b58300384b3
raytsystem-security-review is a skill published in the GitHub repository romarayt/raytsystem-public-os (149 stars, last pushed 18d ago), licensed Apache-2.0. It adds 69 tokens to every session and 465 once invoked, about $0.0003 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
rubber-ducky
Use when you've planned a non-trivial change and are about to implement it, finished a complex or multi-file piece of work, just wrote tests, or are stuck on repeated failures or unexpected results — and any time the user says "rubber duck this", "rubber ducky", "get a second opinion", "sanity-check my plan", "poke…
pr-sweep
Use when you want to sweep all open pull requests across all repos, triage their status, run code reviews on unreviewed PRs, merge what's ready, fix quick blockers, and produce a full status report. Trigger when the user says "check my PRs", "close out open PRs", "what's the status of my PRs", "sweep my PRs", "PR…
review
Use when user invokes /review to review code changes. Also triggers on "review my code", "check this PR", "look at my changes". Accepts a PR number (e.g. /review 123), a path filter (e.g. /review src/auth/), or no argument (reviews current branch vs base). Produces structured per-file review with severity labels…
open-pr
Use when wrapping up a development task and getting a PR ready — runs local tests, creates a PR (if one doesn't exist) with a structured description template, conducts a code review via the review skill, and checks CI status with quick fixes. Trigger when the user says they're done with a feature, want to open a PR…
agent-review
Use in /implement after committing, inside the draft PR, to review the committed diff. Dispatches a dependency-free review subagent fed the diff + review criteria and returns structured findings (severity / location / problem / fix). The recipe drives the address→re-review loop with a human exit gate; the…
review
Adversarial design review of a System Design Doc. Interrogates the staff questions, finds the cost-explosion and failure risks, returns a verdict. Sensors and evals gate.