magus-agent
Install the knowledge-graph agent skills into a repository
Synopsis
magus agent <install|sample|adoption> [flags]
Description
Render the agent skills embedded in this binary and write or stream them into named destinations (.claude/skills, .agents/skills, .opencode/skills, and so on).
magus never writes your AGENTS.md. That file is yours, and an installer that edits a file you own leaves bytes you did not write and cannot audit. So install PRINTS the managed magus block for you to paste, and only when your AGENTS.md is missing it or is carrying a stale one. sample prints a starter AGENTS.md to stdout for you to own and tweak, and never writes a file.
agent is a pure data generator, which is what makes --tar the general answer: it streams a tar archive to stdout, so skills can be installed anywhere a shell can reach. The write-to-disk form exists for the in-repo, paths-relative-to-<dir> case. Absolute destinations are refused unless --global is set, so magus cannot silently write outside the working tree.
adoption reads a corpus of shell commands, one per line, from stdin or from --commands <file>, and reports how often the graph was reached versus a raw text search. -o json emits the report as one object keyed total, graph_verbs, text_searches, search_of_source, search_of_prose, file_reads, magus_runs, other, and top_symbol_greps. Each top_symbol_greps entry carries pattern, count, and run - the graph command to try for that pattern, routed by its shape: magus query for a diagnostic code or a Buzz op, which magus refs (compiled-language symbols only) would miss, and magus refs otherwise. The text report prints the same command after each pattern, and run is empty for a pattern no graph verb fits.
Options
- --dir string (default: .)
- Repo directory to install into (agent install)
- --dry-run
- Print what would be written and removed without touching the filesystem (agent install)
- --force
- Overwrite existing installed skill files (agent install)
- --global
- Allow absolute destination paths in write mode (agent install)
- --prune
- Also remove installed skills this binary no longer ships; without it they are reported and left in place, and only skills magus wrote are ever candidates (agent install)
- --tar
- Stream a tar archive to stdout instead of writing files (agent install)
agent adoption options
- --commands string
- File of shell commands, one per line; without it the corpus is read from stdin
Subcommands
- install
- Render the embedded skills and write or stream them into named destinations
- sample
- Print a starter AGENTS.md to stdout; never writes a file
- adoption
- Report how often agents used the knowledge graph versus a raw text search
Examples
Install into a repo's agent skills directory
magus agent install .claude/skills
Refresh installed skills
magus agent install .claude/skills --force
Refresh, and drop skills this version no longer ships
magus agent install .claude/skills --force --prune
See what a prune would remove first
magus agent install .claude/skills --prune --dry-run
Install anywhere via tar
magus agent install --tar | tar -xf - -C ~/.config/opencode/skills
Print a starter AGENTS.md
magus agent sample
Measure graph adoption over a corpus of shell commands
magus agent adoption --commands commands.txt
Read the corpus from stdin instead
magus agent adoption < commands.txt
The report as JSON, for a dashboard
magus agent adoption --commands commands.txt -o json
See Also
magus(1), magus-ls(1), magus-describe(1), magus-run(1), magus-x(1), magus-where(1), magus-affected(1), magus-graph(1), magus-query(1), magus-explain(1), magus-path(1), magus-refs(1), magus-watch(1), magus-events(1), magus-status(1), magus-clean(1), magus-vcs(1), magus-doctor(1), magus-config(1), magus-session(1), magus-memory(1), magus-notes(1), magus-diff(1), magus-server(1), magus-mcp(1), magus-buzz(1), magus-completion(1), magus-man(1), magus-init(1), magus-self(1), magus-version(1)