agentleFS
Sign inStart free
somesh-ghaturlesomesh-ghaturle/agentic-boundary-terraform-skills/AGENTS.md

agentic-boundary-terraform-skills

AGENTS.md1 starsChanged 11 days agoApache-2.0View on GitHub

Instructions for any coding agent working on this repository: Claude Code, Codex, Cursor or Windsurf. This repository exists for one thing: human-in-the-loop deployment of agents built from Agentic-AI-Systems, with security review and regulated-environment evidence. Work here serves one of those three pillars, or it does not belong here. These sections configure the engineering skills from mattpocock/skills. Issues live in this repo's GitHub Issues, handled with the gh CLI. See docs/agents/issue-tracker.md. The five default labels: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,542 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep every change on the task asked.

    line 9
  2. Very specific:

    Never weaken a lock. The guard in skills/terraform-boundary/hooks/guard.py, the terminal check and fingerprint in boundary.sh apply, and …

    line 10
  3. Very specific:

    Every change to skills/terraform-boundary/, hooks/ or install.py runs bash tests/test_boundary.sh and python3 -m unittest …

    line 12

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

AGENTS.md

Instructions for any coding agent working on this repository: Claude Code, Codex, Cursor or Windsurf.

Scope of this repository

This repository exists for one thing: human-in-the-loop deployment of agents built from Agentic-AI-Systems, with security review and regulated-environment evidence. Work here serves one of those three pillars, or it does not belong here.

  • Keep every change on the task asked. Do not refactor, rename or "improve" anything else in the same change.
  • Never weaken a lock. The guard in skills/terraform-boundary/hooks/guard.py, the terminal check and fingerprint in boundary.sh apply, and the advice to give the agent read-only cloud credentials all stay.
  • A request outside the three pillars gets one sentence saying so, and no work.
  • Every change to skills/terraform-boundary/, hooks/ or install.py runs bash tests/test_boundary.sh and python3 -m unittest tests/test_guard.py tests/test_state.py tests/test_install.py before it is committed.

Agent skills

These sections configure the engineering skills from mattpocock/skills.

Issue tracker

Issues live in this repo's GitHub Issues, handled with the gh CLI. See docs/agents/issue-tracker.md.

Triage labels

The five default labels: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See docs/agents/triage-labels.md.

Domain docs

Single-context: one CONTEXT.md and docs/adr/ at the repo root. See docs/agents/domain.md.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free