Claude Cursor opencode Skill

control-kody

Drive and verify the Kody app with a Feature Map and one CLI. Use when changing UI, account routes, preview deploys, or proving a Cloud Agent change with a real origin, session, and /health SHA.

LLM Mart · 0 points · 0 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download modem-dev-ossrules-public_files_kody_.agents_skills_control-kody-d2b6775.zip · 1 KB

modem-dev/ossrules 29 1 forks MIT Updated 5d ago

Part of modem-dev/ossrules — 39 skills

Install

skills CLI npx skills add https://github.com/modem-dev/ossrules/tree/main/public/files/kody/.agents/skills/control-kody

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install modem-dev-ossrules@llmmart

Git git clone https://github.com/modem-dev/ossrules.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole modem-dev/ossrules collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

control-kody

Do not invent a throwaway curl script, scrape PR comments by hand, or rediscover account routes from routes.ts. Use the CLI and the Feature Map.

node tools/control-kody.ts doctor
node tools/control-kody.ts dev
node tools/control-kody.ts login
node tools/control-kody.ts request GET /account/waiting.json
node tools/control-kody.ts map waiting
node tools/control-kody.ts health --sha <merge-sha>
node tools/control-kody.ts preview -- --request 'GET /account/waiting.json' --check /account/waiting
node tools/control-kody.ts package-create --origin <preview> --package-name <leaf-or-@scope/leaf> [--head-ahead]

--kody-id is an alias for --package-name. npm run control-kody -- <command> is the same entry.

Feature Map

references/features/README.md is the human-readable index. tools/control-kody/feature-catalog.ts is the machine-readable source. map --check (and its node test) fail when a listed path leaves routes.ts or a required HTML route has no entry.

Load one feature file for the surface you are changing.

Seed users

Local: jane@example.com / ilikecode (non-admin)
Preview: me@kentcdodds.com / ilikecode (non-admin, empty until you create data through JSON APIs, or package-create for a saved package)
/admin 403 and /mcp 401 are expected for those seeds

Proof

CI green is not enough for a user-visible account change. Prefer:

doctor then dev or preview
request / --check as the seed user with data for this change
A computerUse video or screenshot of the same page
After merge, health --origin https://kody.codes --sha <merge> (full SHA, unique short SHA, or a later descendant HEAD that contains the merge)

See docs/contributing/control-kody.md and preview-manual-test.

Files (ossrules)

SKILL.md 2.1 KB

---
name: control-kody
description: >
  Drive and verify the Kody app with a Feature Map and one CLI. Use when
  changing UI, account routes, preview deploys, or proving a Cloud Agent change
  with a real origin, session, and /health SHA.
---

# control-kody

Do not invent a throwaway curl script, scrape PR comments by hand, or rediscover
account routes from `routes.ts`. Use the CLI and the Feature Map.

```bash
node tools/control-kody.ts doctor
node tools/control-kody.ts dev
node tools/control-kody.ts login
node tools/control-kody.ts request GET /account/waiting.json
node tools/control-kody.ts map waiting
node tools/control-kody.ts health --sha <merge-sha>
node tools/control-kody.ts preview -- --request 'GET /account/waiting.json' --check /account/waiting
node tools/control-kody.ts package-create --origin <preview> --package-name <leaf-or-@scope/leaf> [--head-ahead]
```

`--kody-id` is an alias for `--package-name`.
`npm run control-kody -- <command>` is the same entry.

## Feature Map

[references/features/README.md](./references/features/README.md) is the
human-readable index. `tools/control-kody/feature-catalog.ts` is the
machine-readable source. `map --check` (and its node test) fail when a listed
path leaves `routes.ts` or a required HTML route has no entry.

Load **one** feature file for the surface you are changing.

## Seed users

- Local: `jane@example.com` / `ilikecode` (non-admin)
- Preview: `me@kentcdodds.com` / `ilikecode` (non-admin, empty until you create
  data through JSON APIs, or `package-create` for a saved package)
- `/admin` 403 and `/mcp` 401 are expected for those seeds

## Proof

CI green is not enough for a user-visible account change. Prefer:

1. `doctor` then `dev` or `preview`
2. `request` / `--check` as the seed user **with data for this change**
3. A computerUse video or screenshot of the same page
4. After merge, `health --origin https://kody.codes --sha <merge>` (full SHA,
   unique short SHA, or a later descendant HEAD that contains the merge)

See
[docs/contributing/control-kody.md](../../../docs/contributing/control-kody.md)
and [preview-manual-test](../preview-manual-test/SKILL.md).