fully async, Tokio-based client.
> **The `nats` crate (synchronous client) is deprecated.** It receives security fixes only. All new
> work happens in `async-nats`. Do not modify the `nats/` directory
Steady13 mentions in 2 weeks
No other project uses it yet
1.6k3y agoReviewMountCreate a free account to mount
exposes Burp operations to external AI agents over the Model Context Protocol (MCP). Targets security professionals running Burp Community or Professional on macOS / Linux / Windows.
**Core Value:** Bring modern
1.6k7mo agoReviewMountCreate a free account to mount
issue #820): operational exceptions are caught and returned as error strings to the LLM; security exceptions (`PermissionError`, `ToolConfirmationRequired`) propagate.
- Pre-execution checks run on every call (not cached): permission validation
1.5k14mo agoReviewMountCreate a free account to mount
commands from another
working directory, use the [fixed command entry](daymade-skill/skill-creator/references/fixed-command-entry.md).
For security scans, use its [absolute owner-script recipe](daymade-skill/skill-creator/references/publishing-and-packaging.md#step-6-security-review).
Before
1.5k27d agoReviewMountCreate a free account to mount
symbol — callers, callees, which execution flows it participates in — use `context({name: "symbolName"})`.
- For security review, `explain({target: "fileOrSymbol"})` lists taint findings (source→sink flows; needs `analyze --pdg`).
## Never
1.5k4mo agoReviewMountCreate a free account to mount
public surface: a new or renamed symbol, a new
parameter, a corrected annotation
- `[security]` — security fixes
- `[docs]` — documentation only
- `[ci]` — what a user installs: the wheels, platforms or sdist contents
No other project uses it yet
1.5k41d agoReviewMountCreate a free account to mount
DATA_DIR` relocates team/task/inbox state but NOT global config.
## Cross-cutting conventions
### Path discipline (security-critical)
Every user-supplied name (team, agent, user, plan ID, inbox recipient…) must flow through
1.5k8mo agoReviewMountCreate a free account to mount
migration `, states the approval, references that record, and passes the same ` `. The built-in security warning on a relayed approval is expected.
- **Wants changes**: dispatch a fresh `orchestrator` with
1.4k4mo agoReviewMountCreate a free account to mount
Summary → Aggressive → Minimal)
- `search` results are capped at Summary level to preserve result quality
- Security tools (`detect_security_issues`, `detect_taint_flows`, etc.) are never compressed
- `get_code_snippet` passes
1.4k3mo agoReviewMountCreate a free account to mount
server. Exposes all REST API and agent RPC.
- `/audit` — Autonomous mobile security audit aligned with OWASP MASTG v2.
## Code Style
Do not generate code splitter comments (or code dividers/dividers)
Prefer
1.4k20d agoReviewMountCreate a free account to mount
picture layering, from the bottom up:
- **Hashing & primitives** — `holo_hash`, `holochain_timestamp`,
`holochain_secure_primitive`, `holochain_util` live in
[holochain-hdi](https://github.com/holochain/holochain-hdi);
`holochain_nonce` in
[holochain
1.4k44d agoReviewMountCreate a free account to mount
A file Claude Code reads at the start of every session. It holds the commands, conventions and warnings the agent needs for this project.
Where does it go?
At the repository root. Claude Code also reads CLAUDE.md files in subdirectories when it works there.
What should it contain?
Build and test commands, the project's layout, conventions that aren't obvious from the code, and mistakes to avoid. Short files tend to work better than long ones.
CLAUDE.md or AGENTS.md?
Claude Code reads CLAUDE.md; most other agents read AGENTS.md. Many projects keep one and point the other at it.