Borrowing it
Nothing to install: this file belongs to YankielDBC2/saas-cybersecurity. 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/YankielDBC2/saas-cybersecurity/main/AGENTS.mdgit clone --depth 1 https://github.com/YankielDBC2/saas-cybersecurityWrote 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/yankieldbc2/saas-cybersecurity/agents-md)<a href="https://agentmods.dev/instructions/yankieldbc2/saas-cybersecurity/agents-md"><img src="https://agentmods.dev/badge/instructions/yankieldbc2/saas-cybersecurity/agents-md/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/instructions/yankieldbc2/saas-cybersecurity/agents-md"><img src="https://agentmods.dev/badge/instructions/yankieldbc2/saas-cybersecurity/agents-md.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.00335 | $0.00335 |
| Opus 5.5 | $0.00134 | $0.00134 |
| Sonnet 5.5 | $0.00067 | $0.00067 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
saas-cybersecurity 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 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.
What it actually says
Agent working agreement
Purpose
Maintain saas-cybersecurity as a portable, defensive Agent Skill for evidence-based SaaS security review and safe remediation.
Rules
- Keep
SKILL.mdconcise and route detailed material intoreferences/. - Preserve compatibility with Codex and Claude Code's filesystem-based Agent Skill format.
- Keep runtime scripts dependency-free on Node.js 18 or newer.
- Treat static matches as triage evidence, not confirmed vulnerabilities, unless the evidence is intrinsically conclusive.
- Never add real secrets, live targets, private reports, exploit payloads, destructive probes, or instructions for unauthorized access.
- Update the control catalog, platform compatibility guidance, tests, and documentation together when behavior changes.
- Run
npm test,npm run validate, and the upstream skill validator before release. - Do not publish or release without reviewing
git diff,git status, and a secret scan.
Repository map
SKILL.md: portable skill entrypoint and safety workflow.references/: detailed controls, platform routing, browser/runtime checks, safe hardening, and report format.scripts/audit.mjs: dependency-free static triage and platform detection.scripts/test-audit.mjs: deterministic behavior tests.scripts/validate-repository.mjs: package integrity and documentation validation.agents/openai.yaml: Codex UI metadata.docs/: maintainer-oriented architecture and project context.
Definition of done
Changes are scoped, documented, cross-platform where practical, tested, free of secrets, and do not turn uncertain evidence into false assurance.
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 · 31 lines · 335 tokens per session scan A 56a4fcc6db80
saas-cybersecurity AGENTS.md is an instructions file published in the GitHub repository YankielDBC2/saas-cybersecurity (2 stars, last pushed 2mo ago), licensed MIT. It adds 335 tokens to every session, about $0.0013 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-08-31.
Other instructions, from other repositories
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core 10, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.