security-check

A security-scanning skill for Python projects that checks code, configuration, and data sent to language-model services for exposed credentials, unsafe patterns, and personal-information leaks.

In plain words
What is it for?
Use it before commits, after changing .env or .gitignore files, when adding API integrations, or when reviewing code that handles credentials or external language-model APIs.
Why use it?
It helps find API keys, tokens, passwords, and sensitive data before they are committed or sent outside the project.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/benkapner/claude-code-basecamp/security-check
Any agent
npx skills add Benkapner/claude-code-basecamp --skill security-check
Clone the repo
git clone --depth 1 https://github.com/Benkapner/claude-code-basecamp

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 247 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00058 $0.00247
Opus 5 $0.00029 $0.00123
Sonnet 5 $0.00012 $0.00049
Haiku 4.5 $0.00006 $0.00025

Measured 3d ago against content hash 8dffc8debb8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

security-check 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 3d 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.

skills/security-check/SKILL.md · 31 lines

What it actually says

Security Check Skill

Scan for credential leaks, insecure code patterns, and LLM security issues in Python data science projects.

When to Activate

  • Before committing changes
  • After modifying .env, .gitignore, or config files
  • When adding new API integrations or credentials
  • When reviewing code that handles tokens, keys, or passwords
  • When code sends data to external LLM APIs (Gemini, OpenAI, etc.)
  • Periodic security hygiene checks

Check Process

Read skills/scan-process.md for the full 6-step scan process with bash commands.

Pattern Reference

Read skills/pattern-tables.md for API key regex patterns, insecure Python code patterns, and LLM-specific security patterns with severity classifications.

Behavioral Rules

Read guidelines.md for severity classifications, remediation requirements, and escalation rules.

Files

What ships with it

3 files 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.

Changes

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.

  1. 3d ago First seen · 31 lines · 58 tokens per session scan A 8dffc8debb8e

Subscribe to this mod's changes

security-check is a skill published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 13d ago), licensed MIT. It adds 58 tokens to every session and 247 once invoked, about $0.0003 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-08-30.

Related

Other skills, from other repositories

manager

Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).

serejaris/personal-corp-os · 63 tokens

weekly-retro

Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.

serejaris/personal-corp-os · 49 tokens

art-director

Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.

serejaris/personal-corp-os · 26 tokens

corp-doctor

Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…

serejaris/personal-corp-os · 102 tokens

html-draft

Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…

serejaris/personal-corp-os · 130 tokens

idea

Use when capturing ONE new idea the user voices and wants recorded — "save this idea", "I have an idea", "log this idea", "/idea", "idea: ...". Creates a provenance-tracked folder (one folder per idea) in your ideas repo, dedups against an index, optionally mirrors to a GitHub Project view filtered by label:idea. NOT…

serejaris/personal-corp-os · 135 tokens