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 ersinkoc/security-check --skill sc-orchestratorgit clone --depth 1 https://github.com/ersinkoc/security-checkWrote 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/ersinkoc/security-check/sc-orchestrator)<a href="https://agentmods.dev/skills/ersinkoc/security-check/sc-orchestrator"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-orchestrator/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/ersinkoc/security-check/sc-orchestrator"><img src="https://agentmods.dev/badge/skills/ersinkoc/security-check/sc-orchestrator.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.00019 | $0.02694 |
| Opus 5.5 | $0.00008 | $0.01078 |
| Sonnet 5.5 | $0.00004 | $0.00539 |
| Haiku 4.5 | $0.00002 | $0.00269 |
Grade A, and why
sc-orchestrator 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SC: Security Check Orchestrator
Purpose
The orchestrator is the central coordination skill for the security-check pipeline. It manages the execution of all scanning phases, dispatches vulnerability detection skills, tracks explicit coverage, aggregates results, and keeps incomplete work visible when individual skills encounter errors.
Apply this evidence contract throughout the pipeline: patterns create candidates, only independently verified trust-boundary failures become confirmed findings, and unavailable decisive facts remain needs_validation without severity. The source distribution includes the expanded rationale in docs/EVIDENCE_MODEL.md.
Operating Modes
- Guidance mode: security questions, focused reviews, triage, and investigation use only relevant skills and do not automatically create the full report tree.
- Full audit mode: explicit repository audits, penetration tests, comprehensive reviews, or requested report artifacts run the complete four-phase pipeline.
- Diff mode: changed-file or PR requests delegate to
sc-diff-reportand disclose their partial scope.
Activation
This skill activates when the user issues any of the following commands:
- "run security check"
- "scan for vulnerabilities"
- "security audit"
- "full security scan"
For diff/incremental mode, see sc-diff-report.
Pre-Check (Phase 0)
Before starting a scan:
Interactive Setup
Honor profile, scope, validation, and prior-report choices already present in the request.
For unresolved choices, use the host's structured question tool in one grouped call. In
Claude Code use AskUserQuestion so the choices render as native selection cards:
- Profile: Standard (recommended), Quick, Deep.
- Scope: Whole repository (recommended), Changed files, Custom paths.
- Validation: Source only (recommended), Sandboxed local checks.
- Previous report, when present: Continue and revalidate (recommended), Archive and start new, Replace.
Request a custom path only if that option is chosen. Selecting Changed files delegates to
sc-diff-report. Selecting Replace is the required explicit authorization to replace prior
artifacts; otherwise preserve them. If structured questions are unavailable, use standard,
whole-repository, source-only, and continue/revalidate defaults unless the user specified
otherwise. Do not ask again for facts already supplied.
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 Changed · +54 lines ee5ffc6960b9
- 1mo ago First seen · 200 lines · 19 tokens per session scan A b7358c5bf289
sc-orchestrator is a skill published in the GitHub repository ersinkoc/security-check (85 stars, last pushed 25d ago), licensed MIT. It adds 19 tokens to every session and 2,694 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…