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 NOMARJ/sigil --skill insecure-defaultsgit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/insecure-defaults)<a href="https://agentmods.dev/skills/nomarj/sigil/insecure-defaults"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/insecure-defaults/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/nomarj/sigil/insecure-defaults"><img src="https://agentmods.dev/badge/skills/nomarj/sigil/insecure-defaults.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.00076 | $0.00713 |
| Opus 5.5 | $0.00030 | $0.00285 |
| Sonnet 5.5 | $0.00015 | $0.00143 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
insecure-defaults 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Insecure Defaults Scanner
Adapted from Trail of Bits' insecure-defaults skill. Layer 1 automated scan — runs on every change, zero human intervention.
What You're Looking For
Hardcoded Credentials
- API keys, tokens, passwords in source code
- Connection strings with embedded passwords
- Private keys, certificates, or secrets committed to repo
.envfiles or secret configs in version control- Base64-encoded credentials (people think encoding = hiding)
Fail-Open Patterns
- Authentication that defaults to "allow" on error
- Authorization checks with catch-all
truereturns - CORS set to
*in production configs - Security middleware that can be bypassed with specific headers
- Feature flags that default to "enabled" for premium features
Dangerous Defaults
- Debug mode enabled in production configs
- Verbose error messages exposing internals
- Default admin credentials still active
- HTTPS not enforced (HTTP fallback allowed)
- Session tokens with excessive lifetimes
- Missing rate limiting on authentication endpoints
- Permissive Content-Security-Policy headers
Configuration Issues
- Production configs committed alongside development configs
- Secrets in docker-compose files, Kubernetes manifests, or CI configs
- Database connections without SSL/TLS enforcement
- Logging configuration that captures sensitive data (PII, tokens, passwords)
Scan Protocol
1. Identify all files in the change set
2. For each file, apply pattern matching:
- Regex patterns for common secret formats (AWS keys, JWT tokens, etc.)
- AST analysis for authentication/authorization logic patterns
- Config file analysis for dangerous settings
3. Classify findings:
- CRITICAL: Hardcoded secret or credential → Block commit
- WARNING: Fail-open pattern or dangerous default → Flag for review
- INFO: Potential issue, needs context → Log
4. Output findings in structured format
Common False Positives
These look like secrets but usually aren't — verify before flagging:
- Example/placeholder values in documentation or tests (
sk_test_...,AKIAIOSFODNN7EXAMPLE) - Hash constants (SHA-256 of known values)
- Base64-encoded non-secret data
- Environment variable references (
process.env.SECRETis fine; the actual value is not)
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 · 82 lines · 76 tokens per session scan A 6d1adf9d635d
insecure-defaults is a skill published in the GitHub repository NOMARJ/sigil (6 stars, last pushed 11d ago), licensed Apache-2.0. It adds 76 tokens to every session and 713 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-09-04.
Other skills, from other repositories
sftp-cc
A natural-language SFTP tool for uploading local project files to a remote server. SFTP is a secure way to transfer files, and this tool supports incremental uploads, private-key binding, and permission fixes.
memory
Retrieve relevant durable BB memories or save verified knowledge useful to future threads.
thread-list
Inspect or change the sidebar thread list's layout preferences: organization mode, sort, section order, hidden groups, collapsed groups, and thread row actions.
workflows
Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.
jk
Manage Jenkins controllers with jk, including jobs, runs, logs, artifacts, credentials, nodes, queues, and plugins.
url
Fetch and extract text from web URLs.