ai-security-crew: Instructions file for Codex

AGENTS.md

ai-security-crew AGENTS.md is an instructions file for Codex, OpenCode from Srajangpt1/ai-security-crew. It costs 1,058 tokens per session, scanned A, original, MIT.

Repository instructions for AI Security Crew, a Python project that reviews software and integrations for security risks, including Atlassian services such as Jira and Confluence. They require a security review before coding begins.

In plain words
What is it for?
Performing task or ticket security assessments, reviewing new features such as file handling and authentication, and extending the security tools.
Why use it?
They establish a repeatable security check and show where providers, data models, servers, tests, and authentication code live.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is Srajangpt1/ai-security-crew's own configuration. It tells Codex and OpenCode how to work on ai-security-crew itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-security-crew configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Srajangpt1/ai-security-crew/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/Srajangpt1/ai-security-crew

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for ai-security-crew AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/srajangpt1/ai-security-crew/agents-md.svg)](https://agentmods.dev/instructions/srajangpt1/ai-security-crew/agents-md)
Your own site
<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>
Per session 1,058 This file is loaded in full into every session.
When invoked 1,058 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01058 $0.01058
Opus 5 $0.00529 $0.00529
Sonnet 5 $0.00212 $0.00212
Haiku 4.5 $0.00106 $0.00106

Measured 8d ago against content hash 8fd6cd45a3ce, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

AGENTS.md · 122 lines

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 instructions field on connect. Changes here should stay in sync with servers/main.py.

Before starting any coding task

  • Call lightweight_security_review with the task description and tech stack.
  • If working from a Jira ticket, call assess_ticket_security instead.
  • 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:

  1. Verify packages exist — call verify_packages. Fix any invalid packages before proceeding.
  2. Scan for vulnerabilities — call scan_dependencies in parallel with verify_code_security, passing the packages and code snippets where they are used. Act on results:
    • reachable or uncertain → upgrade or avoid the vulnerable function before continuing
    • not_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_security with the generated code. Follow the review_prompt in the response to perform the analysis and report findings.

Read the full file on GitHub · 122 lines

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. 8d ago First seen · 122 lines · 1,058 tokens per session scan A 8fd6cd45a3ce

Subscribe to this mod's changes

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.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens