Skip to content
Back to search

codely

Codely’s plugins to level up your code.

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/CodelyTV/agent-harness with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/CodelyTV/agent-harness'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/codelytv--agent-harness/badge.svg)](/listings/codelytv--agent-harness)

HTML

<a href="/listings/codelytv--agent-harness"><img src="/api/listings/codelytv--agent-harness/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

1. Install the skills with the `skills.sh` installer:

   npx skills@latest add codelytv/agent-harness

2. Pick the skills you want and the coding agents you want to install them on.

3. Run a skill in your agent, for example `/codely-doc-create`.

4. Done. Your agent now follows Codely's conventions.

Alternative: Claude Code plugin

1. Add this repository as a plugin marketplace and install the plugin:

   /plugin marketplace add CodelyTV/agent-harness
   /plugin install codely-skills@codely

2. Run a skill in Claude Code, for example `/codely-doc-create`.

3. Done. Every skill in this repo is now available in Claude Code.

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

.claude-plugin/marketplace.json · Manifest · 48 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. {
  2. "name": "codely",
  3. "description": "Codely’s plugins to level up your code.",
  4. "owner": {
  5. "name": "Codely",
  6. "email": "support@codely.com",
  7. "url": "https://codely.com"
  8. },
  9. "plugins": [
  10. {
  11. "name": "codely-skills",
  12. "source": "./",
  13. "description": "Codely's team skills: planning, docs, OpenSpec, and git conventions.",
  14. "category": "engineering"
  15. },
  16. {
  17. "name": "ste100",
  18. "description": "Makes the agent answer in ASD-STE100 Simplified Technical English.",
  19. "version": "1.0.0",
  20. "source": "./.claude/plugins/ste100",
  21. "category": "productivity"
  22. },
  23. {
  24. "name": "ts7-lsp",
  25. "description": "TypeScript/JavaScript code intelligence via the TypeScript 7 native compiler LSP, much faster than tsserver on large monorepos",
  26. "version": "2.0.0",
  27. "source": "./.claude/plugins/ts7-lsp",
  28. "category": "development",
  29. "strict": false,
  30. "lspServers": {
  31. "ts7": {
  32. "command": "tsc",
  33. "args": ["--lsp", "-stdio"],
  34. "extensionToLanguage": {
  35. ".ts": "typescript",
  36. ".tsx": "typescriptreact",
  37. ".js": "javascript",
  38. ".jsx": "javascriptreact",
  39. ".mts": "typescript",
  40. ".cts": "typescript",
  41. ".mjs": "javascript",
  42. ".cjs": "javascript"
  43. }
  44. }
  45. }
  46. }
  47. ]
  48. }
README.md · README · 212 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.

  1. <p align="center">
  2. <a href="https://codely.com">
  3. <picture>
  4. <source media="(prefers-color-scheme: dark)" srcset="https://codely.com/logo/codely_logo-dark.svg">
  5. <source media="(prefers-color-scheme: light)" srcset="https://codely.com/logo/codely_logo-light.svg">
  6. <img alt="Codely logo" src="https://codely.com/logo/codely_logo.svg">
  7. </picture>
  8. </a>
  9. </p>
  10. <h1 align="center">🤖 Agent Harness</h1>
  11. <p align="center">
  12. <a href="https://github.com/CodelyTV"><img alt="Codely OS" src="https://img.shields.io/badge/Codely-OS-green?style=flat-square"></a>
  13. <a href="https://codely.com/cafe"><img alt="Codely Cafe News" src="https://img.shields.io/badge/Codely-Cafe_News-%235A3E2B?style=flat-square"></a>
  14. <a href="https://codely.com/newsletter"><img alt="Codely Newsletter" src="https://img.shields.io/badge/Codely-Newsletter-%23D3D3D3?style=flat-square"></a>
  15. <a href="https://youtube.com/codelytv"><img alt="Codely YouTube" src="https://img.shields.io/badge/Codely-YouTube-red?style=flat-square"></a>
  16. <a href="https://codely.com/courses"><img alt="Codely Courses" src="https://img.shields.io/badge/Codely-Courses-black?style=flat-square"></a>
  17. <a href="https://github.com/CodelyTV/agent-harness/stargazers"><img alt="GitHub Repo stars" src="https://img.shields.io/github/stars/codelytv/agent-harness"></a>
  18. </p>
  19. <p align="center">
  20. Skills, plugins and hooks so your agent writes the code you expect, the way you expect.<br>
  21. </p>
  22. Your agent writes code faster than you can review it. Instead of reading every line, turn your conventions into rules
  23. that fail in seconds: the agent corrects itself, and you review what the change does, not how it is written. Review outputs, not code.
  24. ## Workflow
  25. 1. **Make your docs deterministic** with `/deterministify docs`.
  26. 2. **Enforce your code conventions** with `/deterministify conventions`.
  27. 3. **Add a new rule** with `/create-rule` every time you correct the agent.
  28. 4. **Commit** with `/git-commit`.
  29. 5. **Open the pull request** with `/create-pull-request`, with before/after evidence of what the change does: screenshots, videos and architecture diagrams.
  30. For larger tasks, plan the work with `/create-plan` and implement it one phase at a time with
  31. `/implement-plan-phase`. Already using [OpenSpec](https://openspec.dev)? Run `/openspec-create-spec-from-code` first.
  32. ## Why
  33. ### Your docs are suggestions
  34. You wrote your conventions down, but the agent only follows them if it loads the right doc and reads it the way your
  35. team does.
  36. **The fix:** `/deterministify docs` turns every convention that code can check into a linter rule or a test.
  37. ### Your code does the same job in two ways
  38. A legacy way and a current way live together, and the agent copies whichever it reads first.
  39. **The fix:** `/deterministify conventions` finds them in the code and its history, and enforces the current way with a
  40. rule, after you confirm it.
  41. ### You correct the same thing again and again
  42. You fix the agent in one session, and it makes the same mistake in the next one.
  43. **The fix:** run `/create-rule` after the correction. It becomes a rule when a rule can check it, and a minimal doc
  44. with the reason when it cannot.
  45. ### The history is a mess
  46. Commit messages follow whatever the agent felt like that day.
  47. **The fix:** `/git-commit` writes Conventional Commits with the co-author trailer of the agent that made the change.
  48. ## Install
  49. ```bash
  50. npx skills@latest add codelytv/agent-harness
  51. ```
  52. Pick the skills you want and the agents to install them on. Then run one, for example `/create-rule`.
  53. <details>
  54. <summary>Claude Code plugin</summary>
  55. ```
  56. /plugin marketplace add CodelyTV/agent-harness
  57. /plugin install codely-skills@codely
  58. ```
  59. </details>
  60. ## Skills
  61. | Skill | Use it when | Variants |
  62. |--------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------|------------------------------------|
  63. | [`deterministify`](.agents/skills/deterministify/SKILL.md) | You want the conventions your repository already has enforced by linter rules and tests. | aliases |
  64. | [`create-rule`](.agents/skills/create-rule/SKILL.md) | You corrected the agent, or want a new convention enforced, and want a rule instead of a doc. | |
  65. | [`git-commit`](.agents/skills/git-commit/SKILL.md) | You want to commit your changes with a Conventional Commit message. | |
  66. | [`create-pull-request`](.agents/skills/create-pull-request/SKILL.md) | You open or update a pull request and want its description to follow a template with evidence. | |
  67. | [`create-plan`](.agents/skills/create-plan/SKILL.md) | You start a larger task and want a plan split into reviewable phases. | `-subagents`, `-github`, `-gitlab` |
  68. | [`implement-plan-phase`](.agents/skills/implement-plan-phase/SKILL.md) | You have a plan and want to implement its next phase. | `-github`, `-gitlab` |
  69. | [`openspec-create-spec-from-code`](.agents/skills/openspec-create-spec-from-code/SKILL.md) | You need the OpenSpec specs of behaviour that already exists in the code. | |
  70. | [`create-doc`](.agents/skills/create-doc/SKILL.md) | Deprecated: use `create-rule`. | |
  71. <details>
  72. <summary>Variants</summary>
  73. - aliases: [`docs-to-rules`](.agents/skills/docs-to-rules/SKILL.md) runs `deterministify docs`, and
  74. [`conventions-to-rules`](.agents/skills/conventions-to-rules/SKILL.md) runs `deterministify conventions`. Both
  75. need `deterministify` installed next to them.
  76. - `-subagents`: [`create-plan-subagents`](.agents/skills/create-plan-subagents/SKILL.md) delegates the codebase
  77. exploration to cheaper subagents running in parallel.
  78. - `-github`: [`create-plan-github`](.agents/skills/create-plan-github/SKILL.md) stores the plan as a parent issue with
  79. one sub-issue per phase, and [`implement-plan-phase-github`](.agents/skills/implement-plan-phase-github/SKILL.md)
  80. opens one pull request per phase.
  81. - `-gitlab`: [`create-plan-gitlab`](.agents/skills/create-plan-gitlab/SKILL.md) and
  82. [`implement-plan-phase-gitlab`](.agents/skills/implement-plan-phase-gitlab/SKILL.md) do the same with GitLab issues
  83. and merge requests.
  84. </details>
  85. <details>
  86. <summary><code>codely-spec-plan</code> OpenSpec schema</summary>
  87. An [OpenSpec custom schema](https://github.com/Fission-AI/OpenSpec/blob/main/docs/customization.md) that brings the
  88. `create-plan-subagents` flow to OpenSpec. Each change produces only two things to review:
  89. - **Lean specs**: one behaviour with SHALL per requirement and a single-line scenario.
  90. - **`plan.md`**: goal, decisions and one vertical slice phase per part a user can complete a goal with, each with its
  91. contracts and a test strategy that proves it with few tests. Its checkboxes are the task list that
  92. `/openspec-apply-change` works through one phase per run, committing each phase.
  93. Install it in your project and select it in `openspec/config.yaml`:
  94. ```bash
  95. npx degit CodelyTV/agent-harness/openspec/schemas/codely-spec-plan openspec/schemas/codely-spec-plan
  96. ```
  97. ```yaml
  98. schema: codely-spec-plan
  99. ```
  100. </details>
  101. ## Claude Code plugins
  102. Plugins for Claude Code only, installed from this repository's marketplace.
  103. <details>
  104. <summary><code>ste100</code>: answers in Simplified Technical English</summary>
  105. Makes the agent write to you in [ASD-STE100 Simplified Technical English](https://www.asd-ste100.org/): short
  106. sentences, active voice, one word per meaning, no idioms. It changes how the agent writes to you, not how it writes
  107. code.
  108. ```
  109. /plugin marketplace add CodelyTV/agent-harness
  110. /plugin install ste100@codely
  111. ```
  112. Then run `/config`, look for **Output Style**, and select `ASD-STE100`. More in its
  113. [README](.claude/plugins/ste100/README.md).
  114. </details>
  115. <details>
  116. <summary><code>ts7-lsp</code>: faster TypeScript code intelligence</summary>
  117. Go-to-definition, references and diagnostics through the
  118. [TypeScript 7 native compiler](https://devblogs.microsoft.com/typescript/announcing-typescript-7-0/) LSP. It indexes
  119. large monorepos roughly 10x faster and with far less CPU than the official `typescript-lsp` plugin.
  120. Requires a TypeScript 7+ `tsc` binary on `PATH` (e.g. `npm install -g typescript`).
  121. ```
  122. /plugin marketplace add CodelyTV/agent-harness
  123. /plugin install ts7-lsp@codely
  124. /plugin disable typescript-lsp@claude-plugins-official
  125. ```
  126. More in its [README](.claude/plugins/ts7-lsp/README.md).
  127. </details>
  128. ## Under the hood
  129. <details>
  130. <summary>One source for every agent</summary>
  131. Rules live in `AGENTS.md` and skills in `.agents/skills/`. Each agent expects them in a different path, so a `make`
  132. command creates the symlinks it needs. They are not committed, so run the ones you need after cloning:
  133. | Command | What it does |
  134. |--------------------------|-------------------------------------------------------------------------------------------------|
  135. | `make claude-symlinks` | Links `CLAUDE.md → AGENTS.md` in every directory with an `AGENTS.md`, and `.claude/skills` |
  136. | `make codex-symlinks` | Links `.codex/skills → .agents/skills` |
  137. | `make copilot-symlinks` | Links `.github/skills → .agents/skills` |
  138. | `make cursor-symlinks` | Links `.cursor/skills → .agents/skills` |
  139. | `make junie-symlinks` | Links `.junie/skills → .agents/skills` |
  140. | `make opencode-symlinks` | Links `.opencode/skills → .agents/skills` |
  141. </details>
  142. <details>
  143. <summary><code>export</code> blocked via hooks</summary>
  144. The `export` command can leak environment variables (tokens, secrets) if an agent runs it. Each agent has a
  145. pre-execution hook that blocks any shell command containing `export`:
  146. | Agent | Hook location | Mechanism |
  147. |-------------|------------------------------------------------------|--------------------------------------------------------------------------------------------------|
  148. | Claude Code | `.claude/settings.json` | Uses the `if` keyword with a glob pattern (`Bash(*export*)`) to match and block inline |
  149. | Cursor | `.cursor/hooks.json` + `hooks/block-export.sh` | Runs a shell script that parses the command via `jq` and exits with code 2 on match |
  150. | Copilot | `.github/hooks/hooks.json` + `hooks/block-export.sh` | Same approach as Cursor, adapted to Copilot's hook input format |
  151. | OpenCode | `.opencode/plugins/block-export.ts` | A native TypeScript plugin (`tool.execute.before`) that inspects the command and throws to block |
  152. </details>

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.