Expand description
Platform probe abstraction.
agentsec-core is designed to support multiple Agent platforms
(Claude Code, Cursor, Codex, Gemini CLI, Copilot, …). Each platform
has its own config layout (target paths, dotfile decomposition rules,
MCP server config schema), and the scan / registry pipeline must be
able to enumerate them without baking platform-specific paths into
the pipeline code.
PlatformProbe is the single trait every platform implements. The
scan / registry / unknown modules consume &dyn PlatformProbe so
that adding a new platform is a matter of writing a new probe impl
(typically in a sibling crate, e.g. agentsec-platform-claude).
§Phase 2 status
agentsec-core now ships no platform implementations. The
Claude Code probe lives in the sibling crate
agentsec-platform-claude; binaries are responsible for
instantiating and registering probes before invoking
crate::scan::run / crate::scan::unknown::classify, which
take &[&dyn PlatformProbe] slices.
Structs§
- Fragment
Entry - One virtual sub-entry produced by
PlatformProbe::decompose_file. - McpServer
Entry - One MCP server entry extracted from a platform-specific config file.
Traits§
- Platform
Probe - One platform’s probe. Implementations are typically owned by a
sibling crate (e.g.
agentsec-platform-claude::ClaudeCodePlatform) and registered with theagentsecbinary at startup.