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 PacificStudio/openase --skill security-scangit clone --depth 1 https://github.com/PacificStudio/openaseWrote 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/pacificstudio/openase/security-scan)<a href="https://agentmods.dev/skills/pacificstudio/openase/security-scan"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/security-scan/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/pacificstudio/openase/security-scan"><img src="https://agentmods.dev/badge/skills/pacificstudio/openase/security-scan.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.00021 | $0.00687 |
| Opus 5.5 | $0.00008 | $0.00275 |
| Sonnet 5.5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
security-scan 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.
How it starts
The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scan
Overview
Conduct a security-focused review of the code or change set. Map trust boundaries first, then inspect how untrusted input, credentials, permissions, dependencies, and deployment defaults are handled.
When To Use
- After adding or changing authentication or authorization logic.
- After adding new API endpoints, uploads, background jobs, or external integrations.
- Before production deployment.
- When the change handles untrusted input, secrets, tokens, files, or network calls.
- When the user explicitly requests a security review or audit.
Review Workflow
-
Map the attack surface.
- Entry points, user-controlled input, file access, network access, storage boundaries, and privileged operations.
-
Review authentication and authorization.
- Authentication bypasses.
- Missing authorization checks.
- Confused trust boundaries between user, service, and admin actions.
-
Review input handling and injection surfaces.
- SQL, NoSQL, shell, template, and path injection.
- XSS and unsafe HTML rendering.
- SSRF, open redirects, and unsafe outbound requests.
-
Review secrets and cryptography.
- Hardcoded keys, tokens, passwords, or connection strings.
- Weak password hashing or unsafe token generation.
- Sensitive data exposure in logs, errors, or client payloads.
-
Review dependency and configuration risk.
- Known vulnerable dependencies.
- Overly permissive defaults.
- Missing secure headers, unsafe CORS, or weak production settings.
-
Review detection and recovery.
- Are important security-relevant failures logged?
- Would an operator be able to detect abuse or investigate an incident?
-
Report severity-rated findings with remediation guidance.
CRITICAL: exploitable issue or active secret exposure; block deployment.HIGH: serious vulnerability or major trust-boundary weakness; fix before release.MEDIUM: meaningful hardening gap or partial control failure.LOW: defense-in-depth improvement or cleanup.
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 · 81 lines · 21 tokens per session scan A 63138340a990
security-scan is a skill published in the GitHub repository PacificStudio/openase (269 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 687 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
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
review
Comprehensive security and correctness audit. Use for review, deep review, thermo nuclear, or thermonuclear requests and branch or PR diff audits.
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.
omh-image-cards
This is an OMH img-summary workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
omh-ai-slop-cleaner
This is an OMH ai-slop-cleaner workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).