Borrowing it
Nothing to install: this file belongs to Srajangpt1/ai-security-crew. 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/Srajangpt1/ai-security-crew/main/AGENTS.mdgit clone --depth 1 https://github.com/Srajangpt1/ai-security-crewWrote 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/srajangpt1/ai-security-crew/agents-md)<a href="https://agentmods.dev/instructions/srajangpt1/ai-security-crew/agents-md"><img src="https://agentmods.dev/badge/instructions/srajangpt1/ai-security-crew/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.1 | $0.01058 | $0.01058 |
| Opus 5 | $0.00529 | $0.00529 |
| Sonnet 5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
ai-security-crew 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 8d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Audience: LLM-driven engineering agents
This file provides guidance for autonomous coding agents working inside the AI Security Crew repository.
Repository map
| Path | Purpose |
|---|---|
src/mcp_security_review/ |
Library source code (Python ≥ 3.10) |
├─ providers/atlassian/ |
Atlassian service providers (Jira, Confluence) |
├─ models/atlassian/ |
Pydantic data models for Atlassian APIs |
├─ servers/ |
FastMCP server implementations |
├─ security/ |
Security assessment and guidelines |
└─ utils/ |
Shared utilities (auth, logging, SSL) |
tests/ |
Pytest test suite with fixtures |
scripts/ |
OAuth setup and testing scripts |
Security tool workflow
Note: This workflow is also delivered to end users automatically via the MCP server's
instructionsfield on connect. Changes here should stay in sync withservers/main.py.
Before starting any coding task
- Call
lightweight_security_reviewwith the task description and tech stack. - If working from a Jira ticket, call
assess_ticket_securityinstead. - For significant new features (auth, file handling, external integrations), also call
perform_threat_model.
When adding or updating packages
Run both steps before writing code that uses the new packages:
- Verify packages exist — call
verify_packages. Fix any invalid packages before proceeding. - Scan for vulnerabilities — call
scan_dependenciesin parallel withverify_code_security, passing the packages and code snippets where they are used. Act on results:reachableoruncertain→ upgrade or avoid the vulnerable function before continuingnot_reachable/not_imported→ note it and continue; consider upgrading anyway
Both SCA tools accept a JSON array of {"name", "version", "ecosystem"} objects ("pypi" or "npm").
After generating code
- Call
verify_code_securitywith the generated code. Follow thereview_promptin the response to perform the analysis and report findings.
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.
- 8d ago First seen · 122 lines · 1,058 tokens per session scan A 8fd6cd45a3ce
ai-security-crew AGENTS.md is an instructions file published in the GitHub repository Srajangpt1/ai-security-crew (68 stars, last pushed 4mo ago), licensed MIT. It adds 1,058 tokens to every session, about $0.0053 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.
Other instructions, from other repositories
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).
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.
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).
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.