Skip to content
Agent Threat Rules (ATR)中文
Contribute

The attack you found can become everyone's rule.

ATR is a public good. Anyone can propose a rule. Once it clears a public PR and the safety gate, it is part of a standard every defender shares. MIT licensed, with no proprietary tooling and no CLA. Start by reporting an evasion. It takes fifteen minutes.

Integrating ATR into your project
Planning or implementing

Open an Integration Request issue

Any engine may implement the standard. This path is for the people building one. The intake form is structured and takes five minutes. Use it when you need a spec walkthrough, a design review, sample code for your language, or a mapping to compliance frameworks. Maintainers respond within seven days.

Open the issue
Already shipped

Open a PR against ADOPTERS.md

Take this path once your integration is public and verifiable. Entries that match the schema and carry a verifiable evidence link get merged. Maintainers do not pre-approve adopters. Sigma works the same way.

ADOPTERS.md
Improve the rules themselves
  1. Submit a new rule (no fork needed)

    Found a new attack pattern? File one issue and a bot turns it into a draft proposal PR. No clone, no YAML.

    Open an issue
  2. Submit a red-team probe

    Have an attack payload and benign look-alikes? If a maintainer reviews and accepts it, they turn it into a proposal PR. Later measurement runs may use your payload, but it is not guaranteed to join a benchmark corpus.

    Submit a probe
  3. Report an evasion

    Found a way past a rule? Every confirmed evasion leads to a rule fix. This is the most impactful kind of contribution.

    Open an issue
  4. Report a false positive

    A rule fired on legitimate content? Report it so the rule can be fixed. The per-lane false-positive rates were withdrawn on 2026-09-19 and are pending re-measurement.

    Open an issue
  5. Write a full rule (advanced)

    Want to write the YAML yourself? Fork the repo, follow the spec, run atr validate and atr test, then open a PR. The guide walks through every step.

    See the guide
  6. Contribute with an AI assistant

    Use Claude Code or Cursor with ATR's MCP server. The AI writes the YAML, and you review it.

    See the MCP setup
What happens after you contribute
  1. New-rule issues: a bot converts your issue into a YAML draft under proposals/ and opens a draft PR with your name in the author field. The other issue types above, red-team probes included, go to a maintainer first. A PR follows only if the maintainer accepts the report.
  2. A maintainer or community member writes the detection regex and runs the safety gate: true- and false-positive samples, schema compliance, no conflict with existing rules, and zero false positives on the benign corpus as a hard requirement. The gate really does block rules.
  3. The rule merges to main and ships in the next release. CI stages it on npm, a maintainer approves it with 2FA, and the GitHub release follows. From then on it belongs to every engine that reads ATR, whatever the vendor or the country.
  4. Later measurement runs may use your payload, but it is not guaranteed to join a benchmark corpus. data/measurements/<source>/ keeps the recall, precision and fp-rate of every run, pinned to a version so the numbers cannot drift.
  5. Every public recall figure ATR cites comes with the path to its measurement file, so your contribution can be traced in the public audit chain.
Want to change the spec itself

The spec (SPEC.md) is the contract between all conforming engines, so changing it is less direct than adding a rule. First open an issue whose title starts with [RFC], saying what you want to change and why. Then leave a 14-day public comment window (30 days for complex proposals) so every implementer can see it and respond. After that, submit the PR. A breaking change (SemVer major bump) also needs 30 days' advance notice.

The full process is under Decision-making on the governance page.

First time contributing

Want to help but not sure where to start? Two easy ways in:

  • Open issues labelled 'good first issue': starter tasks a maintainer has tagged, each with a clear scope.
  • False-positive reports. If a rule misfires in your workflow, a 15-minute report directly helps every downstream adopter. Maintainers put this kind of feedback first.
Want to become a maintainer

ATR has several maintainers, but merging is still concentrated with the lead maintainer, so more are being recruited. The candidate criteria, how decisions are made and how to apply are all on the governance page.

See 'Become a maintainer' on the governance page