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 agentmods add instructions/teehooai/spidershield/agents-mdgit clone --depth 1 https://github.com/teehooai/spidershieldWrote 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/teehooai/spidershield/agents-md)<a href="https://agentmods.dev/instructions/teehooai/spidershield/agents-md"><img src="https://agentmods.dev/badge/instructions/teehooai/spidershield/agents-md.svg" alt="Measured on agentmods" 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 | $0.00735 | $0.00735 |
| Opus 5 | $0.00367 | $0.00367 |
| Sonnet 5 | $0.00147 | $0.00147 |
| Haiku 4.5 | $0.00073 | $0.00073 |
Grade A, and why
spidershield AGENTS.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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — SpiderShield
Security scanner and runtime guard for MCP servers. Static analysis, policy enforcement, DLP, prompt injection detection.
What This Project Does
SpiderShield is an open-source security linter for MCP (Model Context Protocol) servers and AI agent skills. Think "npm audit for MCP tools." It scans tool descriptions, security patterns, architecture quality, and licensing, then outputs a 0-10 SpiderScore.
Quick Start
pip install spidershield
# Scan an MCP server from GitHub
spidershield scan https://github.com/owner/repo
# Check an AI agent config (Claude Code / OpenClaw)
spidershield agent-check /path/to/config
# Run as MCP server (for integration with Claude Desktop, etc.)
spidershield serve
Project Structure
src/spidershield/
cli.py -- Click CLI entry point
models.py -- Pydantic V2 models (ScanReport, SecurityIssue, etc.)
server.py -- MCP server mode (scan_mcp_server tool)
scanner/
runner.py -- 4-stage scan pipeline (descriptions → security → architecture → license)
description_quality.py -- Tool description scoring (7 criteria)
security_scan.py -- 46+ static security patterns
architecture_check.py -- Code quality checks
license_check.py -- License detection
agent/
scanner.py -- Agent config security audit
skill_scanner.py -- Skill malware/injection detection (20+ patterns)
toxic_flow.py -- Dangerous capability combination detection
pinning.py -- SHA-256 content pinning for rug-pull detection
rewriter/
runner.py -- Template + LLM description rewriter
hardener/runner.py -- Security fix suggestions
Build & Test
# Install in dev mode
pip install -e ".[dev]"
# Run tests (use empty env vars to skip Supabase, use local SQLite)
SUPABASE_URL= SUPABASE_SERVICE_KEY= python -m pytest tests/ -x -q
# Run a specific test
python -m pytest tests/test_scanner.py -x -q
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 · 91 lines · 735 tokens per session scan A e0004c30e7e4
spidershield AGENTS.md is an instructions file published in the GitHub repository teehooai/spidershield (10 stars, last pushed 4mo ago), licensed MIT. It adds 735 tokens to every session, about $0.0037 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-31.
Other instructions, from other repositories
raindrop-mcp AGENTS.md
Instructions for adeze/raindrop-mcp, covering raindrop mcp — codex guide, commands, architecture, non-negotiable contracts and codex workflow.
mcp AGENTS.md
AGENTS.md instructions for Teamwork/mcp, covering agents.md, this repository is public, project overview, setup commands and build and run.
raindrop-mcp mcp-inspector.instructions.md
Instructions for adeze/raindrop-mcp, covering mcp inspector cli prompt, prerequisites, usage examples, list available tools and send a protocol request (e.g., ping).
raindrop-mcp GEMINI.md
Instructions for adeze/raindrop-mcp, covering raindrop mcp server - project context, project overview, core technologies, architecture and key commands.
assay CLAUDE.md
Claude Code instructions for Rul1an/assay, covering assay - ai agent context, what is assay?, workspace structure, key commands and cli entry points.
assay AGENTS.md
AGENTS.md instructions for Rul1an/assay, covering assay agent contract, canonical state, adr-042/043 scope, branch and worktree ownership and development discipline.