Constant AGENT_PLUGIN_SKILL 

pub const AGENT_PLUGIN_SKILL: &str = "---\nname: \"{{SKILL_NAME}}\"\ndescription: {{SKILL_DESCRIPTION_YAML}}\n---\n\n# Code System Graph\n\nUse Code System Graph to find relevant repositories and entities, follow\nrelationships, and support conclusions with workspace graph evidence. Confirm\ncurrent behavior in live source, Git state, and focused tests.\n\n## Verify the workspace\n\n1. Use this skill only when the task belongs to workspace `{{WORKSPACE}}` and\n   the nearest relevant `code-system-graph.yaml` declares that name.\n2. Call `status` before any other Code System Graph MCP tool. Confirm the\n   workspace and note freshness, partial coverage, or degradation that affects\n   the task.\n3. If the MCP is unavailable or reports another workspace, stop using it. Do\n   not guess paths or reconfigure graph tooling; continue with live repository\n   evidence and report the limitation.\n\n## Choose the smallest useful tool\n\n| Goal | MCP tool |\n| --- | --- |\n| Find repositories, entities, capabilities, or known terms | `query` |\n| Inspect persisted context for a known entity | `source_context` |\n| Find architectural or subsystem groupings | `communities` |\n| Find a path between two resolved entities | `trace` |\n| Estimate upstream or downstream change risk | `impact` |\n| Inspect or validate API and data contracts | `contracts` |\n| Analyze working-tree or staged changes | `analyze_changes` |\n| Analyze a pull request and cross-repository overlap | `analyze_pull_request` |\n| Inspect repository-local source, symbols, call paths, or tests | `explore`, when available |\n\nUse `query` before tools that require stable node identifiers; never invent an\nidentifier. Keep scopes, depths, and result limits bounded. If results are\nambiguous or truncated, refine the question or paginate before broadening it.\nCall only the tools needed for the current task.\n\n## Use graph evidence correctly\n\n- Use graph results to choose where to inspect and which relationships to\n  verify; do not treat them as a replacement for live code or tests.\n- Verify implementation claims with `explore` or focused source reads. Verify\n  behavior changes with relevant tests when the task requires it.\n- State only freshness, coverage, degradation, or evidence gaps that materially\n  affect the conclusion.\n- Do not infer that an entity or relationship does not exist when the relevant\n  graph layer is stale, partial, unsupported, or capped.\n\n## Keep maintenance explicit\n\nDo not run `scan`, `sync`, `codegraph init`, admin tools, or configuration\nmutations unless the user explicitly requests graph maintenance or repository\nonboarding. For those tasks, read\n[the operating guide](references/operating-guide.md) completely before acting.\nUse live `--help` for the installed versions and make the smallest justified\nchange.\n";

Canonical cross-client Code System Graph skill.