integrate-projectslisted

# Integrate External Projects Configure an opencode project to access multiple external codebases persistently, skipping permission prompts and giving the agent the context it needs to work across them. ## What This Skill Does One thing: **`references` in `opencode.json`**. - opencode injects each described reference's resolved `path` and `description` into the agent's system prompt at session start — the agent knows what each external codebase is and when to consult it without reading any files upfront. The alias key is used for `@` autocomplete. - Referenced directories are automatically added to the `external_directory` allowlist — no permission prompts. - The agent can then freely use `read`/`glob`/`grep` to explore those directories on demand. Do NOT modify the project's `AGENTS.md` for this purpose. `AGENTS.md` belongs to the project's own knowledge. References are the right mechanism: each external project stays independent, the agent integrates them via the reference descriptions. Read-only references are **not supported by this skill**. Current opencode permission behavior can allow edits under referenced external directories even when `permission.edit` deny rules are present. If the user asks for read-only access, stop and explain that this skill will not configure read-only references until opencode can enforce them reliably; continue only if they approve read+write reference access. **Key insight: `references` are automatically allowed.** opencode wires ref