Skip to content

docs: make AGENTS.md an index of the org standards - #131

Open
singlerider wants to merge 3 commits into
blacklanternsecurity:devfrom
singlerider:chore/org-standards-index
Open

singlerider wants to merge 3 commits into
blacklanternsecurity:devfrom
singlerider:chore/org-standards-index

Conversation

@singlerider

@singlerider singlerider commented Oct 3, 2026 •

Copy link
Copy Markdown

Part of blacklanternsecurity/bbot-enterprise#157.

  • AGENTS.md: what the repo is, toolchain, setup, test commands, an index of the org standards with when to read each, and only facts specific to this repo. Versions are referenced in the manifest, not retyped.
  • CLAUDE.md points at AGENTS.md.
  • Tests section states the Chrome prerequisite.

Validation

$ git diff --stat upstream/dev
  AGENTS.md | 43 +++++++++++++++++++++++++++++++++++++++++++
  CLAUDE.md |  1 +
  2 files changed, 44 insertions(+)
$ poetry run pytest -q   (no Chrome installed)
3 failed, 1 passed   (Chrome executable not found, the prerequisite now documented)

Standards links point at blacklanternsecurity/.github/blob/main/standards. They resolve once the standards land in .github and it is made public (admin step).
CI lint fails on upstream dev too (ruff check: Found 70 errors on 39628b9) and is fixed by webcap#132.

Refs blacklanternsecurity/bbot-enterprise#157

Org-wide standards now live once in blacklanternsecurity/.github. This
AGENTS.md states what the repo is, its toolchain and test commands,
links each standard with when to read it, and keeps only what is true
here and nowhere else. CLAUDE.md points at it instead of duplicating
it, so agent context stops paying for restated rules.

Refs blacklanternsecurity/bbot-enterprise#157
The table claimed Python 3.10 through 3.14 while pyproject.toml declares
>=3.9,<3.14, called ruff pinned while it is a range, and said
toolchain.md tracks a uv migration, which it does not. Reference the
manifest and state plainly that the repo is not yet on uv.
Without Chrome or Chromium on PATH, three of four tests fail with
'Chrome executable not found'. Point at possible_chrome_binaries in
webcap/browser.py, which owns the list of names searched.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant