bro / filetypes
AGENTS.md12 starsChanged 13 days agoApache-2.0View on GitHub
bro-filetypes contributes the leaf namespace bro.pdf and registers its TYPE in bro.file_types. Core imports no provider. The declaration imports models only; provider.py and engine.py belong in the worker. The root owns formatting, typing and the gate. Provider tests run in unit; tests through the real confined worker run in sandbox (local/AGENTS.md). Build with uv build --package bro-filetypes. The engine dependency is pinned in this member's metadata; a bump is a security update and requires exercising both rosters.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bench/AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- bro/AGENTS.mdAGENTS.md
- browser/AGENTS.mdAGENTS.md
- dev/AGENTS.mdAGENTS.md
- local/AGENTS.mdAGENTS.md
- oops/AGENTS.mdAGENTS.md
- ride/AGENTS.mdAGENTS.md
The file
Files
File-type providers
bro-filetypes contributes the leaf namespace bro.pdf and registers its TYPE in bro.file_types.
Core imports no provider.
The declaration imports models only; provider.py and engine.py belong in the worker.
Components
bro/pdf/__init__.py— the PDF declaration and details model.bro/pdf/engine.py— direct ctypes bindings, initialized PDFium and scoped document/page/text handles.bro/pdf/page_text.py— assembly of the per-character list into sanitized text and ordered notes.bro/pdf/provider.py— preparation, inspection and view dispatch, including the has-text fast path.bro/pdf/links.py— link enumeration, URI byte display and spatial anchor selection.bro/pdf/attachments.py— declared-text attachment reads and content validation.bro/pdf/form_fields.py— widget values and deterministic nearby-label selection.bro/pdf/view_limits.py— cumulative string and entry accounting for views.bro/pdf/manual.md— the shipped caller reference.bro/pdf/pdf_test_helper.py— stdlib-only PDF generation for tests and checkout benchmarks; excluded from the wheel.bro/pdf/hostile_test_helper.py— stdlib-only hostile corpus generators, one per family; excluded from the wheel.bro/pdf/hostile_corpus_sandbox_test.py— the hostile corpus through the real confined worker, pinning each family's first-run outcome.
Development
The root owns formatting, typing and the gate.
Provider tests run in unit; tests through the real confined worker run in sandbox (local/AGENTS.md).
Build with uv build --package bro-filetypes.
The engine dependency is pinned in this member's metadata; a bump is a security update and requires exercising both rosters.
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
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.

