DevAgentRadar → Repo Harness Rule Patch

Goal: update our repository's permanent harness instructions based on this release.

Update the file that tool actually reads. Do not dump everything into one file.

• Claude Code → CLAUDE.md plus .claude/ (skills, hooks, settings, agents, commands). It does not read AGENTS.md natively; start CLAUDE.md with @AGENTS.md.
• Codex, Copilot, Cursor, Factory Droid, Grok Build, Roo Code, Goose, OpenCode, Amp, Zed, Aider → AGENTS.md.
• Gemini CLI / Antigravity → GEMINI.md. AGENTS.md only if context.fileName is set.
• Cursor glob-scoped rules → .cursor/rules/*.mdc (plain .md is ignored), not a second constitution.
• Codex MCP → .codex/config.toml, not .mcp.json.
• Copilot extra instructions → .github/copilot-instructions.md; custom agents → .github/agents/.
• Windsurf → .windsurf/rules (do not assume AGENTS.md).
• Cline → .clinerules.
• Procedures → a skill (SKILL.md). Enforcement the model must not skip → a hook. Isolated roles → subagents.
• Do not fork the same rule into three tool files.

Context

Assistant: Kilo Code Proposal: Install Marketplace plugins from git:github.com/owner/repo@v1.2.3#subdir sources

Summary: Kilo Code v7.7.9 installs Marketplace plugins from pinned git sources as well as npm. Point catalog entries at git:github.com/owner/repo@v1.2.3#subdir so the client clones that ref into the plugin cache, then install or remove the item in Marketplace for project or global scope.

Primary source: https://github.com/Kilo-Org/kilocode/releases/tag/v7.7.9

Why it matters

Kilo Code v7.7.9 lists plugin items in the Marketplace alongside agents, skills, and MCP servers. Installing a plugin adds the npm package to Kilo's plugin configuration for the chosen project or global scope; removing the item cleans that configuration entry again. Catalog entries can now use a git source such as git:github.com/owner/repo@v1.2.3#subdir, so a plugin can ship from a public repository without publishing to npm. The client clones the repository at the pinned ref into the plugin cache and loads the plugin from there. Move internally shared plugins onto that git form with an explicit tag or commit and optional #subdir, then install once at project scope (use global only when every workspace should load it). That replaces ad-hoc npm publishes and keeps every machine on the same ref.

Suggested actions

1. Upgrade Kilo Code to v7.7.9, then add a Marketplace plugin catalog source git:github.com/OWNER/REPO@v1.2.3#subdir so the client clones that pinned ref into the plugin cache instead of requiring an npm publish.

2. In Kilo Marketplace, install the plugin item for this repository's project scope so it is written into Kilo's plugin configuration; use global scope only if every workspace should load it.

3. Remove Marketplace plugin items you no longer want so Kilo cleans the matching plugin configuration entries.

4. Keep every git catalog source on a tag or commit in the form git:github.com/owner/repo@v1.2.3#subdir, not a floating branch, so the clone stays on the pinned ref.

Config surfaces this release may change

• context and compaction settings (high confidence) — check your repo before applying
• skills — check your repo before applying
• permission rules — check your repo before applying
• MCP servers — check your repo before applying
• subagent definitions — check your repo before applying
• background and headless runs — check your repo before applying

After you finish

Do not report this as applied to DevAgentRadar. You cannot write the visitor's loop.

Tell the human: open https://devagentradar.com/proposals/kilo-code-v7-7-9-install-marketplace-plugins-from-git-github-com-owner-r and mark Applied, Skipped, or Failed. Proposal id: 7d42177d-56f1-4316-b31c-f9249012778f

Instructions:

1. Read the existing context files and settings for the tools in this repo.
2. Draft an explicit Git diff. Update ONLY agent harness rules or tool configuration.
3. Call out deprecated flags, obsolete habits, or changed permission boundaries.
4. Do not touch application logic.

Start with the proposed diff and say which layer and which tool's file it belongs in.