Borrowing it
Nothing to install: this file belongs to Sceptre/sceptre-mcp-server. 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/Sceptre/sceptre-mcp-server/main/.kiro/steering/security-review.mdgit clone --depth 1 https://github.com/Sceptre/sceptre-mcp-serverWrote 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/instructions/sceptre/sceptre-mcp-server/security-review)<a href="https://agentmods.dev/instructions/sceptre/sceptre-mcp-server/security-review"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/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/instructions/sceptre/sceptre-mcp-server/security-review"><img src="https://agentmods.dev/badge/instructions/sceptre/sceptre-mcp-server/security-review.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.00294 | $0.00294 |
| Opus 5 | $0.00147 | $0.00147 |
| Sonnet 5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
sceptre-mcp-server security-review.md 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.
What it actually says
Security Review Skill
Activate this skill to perform a security audit on the codebase or recent changes.
Audit Process
1. Secrets Scan
- Search for hardcoded API keys, passwords, tokens, connection strings
- Check .env files are in .gitignore
- Verify secrets are loaded from
os.environor AWS Secrets Manager - Look for secrets in comments, TODOs, or test files
2. Input Validation Check
- Verify
stack_pathparameters are validated against path traversal - Check that
sceptre_project_diris validated before use - Ensure error messages don't leak sensitive file system paths
3. Dependency Audit
- Run
poetry run pip-audit - Check for known CVEs in dependencies
- Verify
poetry.lockis committed - Remove unused dependencies
4. Dangerous Code Patterns
See security.md for the complete list. During review, flag any matches in changed files.
Output Format
[CRITICAL/HIGH/MEDIUM/LOW] Category — Description
Location: file:line
Risk: What could go wrong
Fix: How to remediate
Emergency Protocol
If CRITICAL vulnerability found:
- Document it immediately
- Fix before any other work
- Rotate exposed secrets
- Check for similar issues elsewhere
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 · 48 lines · 294 tokens per session scan A c1c81df43381
sceptre-mcp-server security-review.md is an instructions file published in the GitHub repository Sceptre/sceptre-mcp-server (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 294 tokens to every session, about $0.0015 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-09-08.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).