concord
v0.9.0-alpha.35Codex harness-engineering tools: session-state checkpoint, cross-session charter, review-until-green, review-until-lgtm, initiative-to-prs, provider-neutral ticket-writing, proposal-package-authoring, and ticket-to-pr.
By arinyahoLicense: MIT2 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 5 skill or MCP entries
- Source updated
- Sep 30, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install concord for Codex
codex plugin marketplace add arinyaho/concord
codex plugin marketplace upgrade arinyaho-concord
codex plugin add concord@arinyaho-concordPaste and run these commands in a terminal with Codex. They add and refresh the arinyaho-concord catalog, then install this plugin.
Compatibility: the page URL and API slug “concord-2” remain stable.
- Codex:
concord-2@agent-plugin-marketplace→concord@arinyaho-concord
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/arinyaho/concordClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/concord-codex/.
Plugin files
├── .codex-plugin/plugin.json├── skills/initiative-to-prs/SKILL.md├── skills/proposal-package-authoring/SKILL.md├── skills/review-until-lgtm/SKILL.md├── skills/ticket-to-pr/SKILL.md└── skills/ticket-writing/SKILL.md
Included Skills5
Use when a product brief, problem report, strategic objective, or set of incomplete tickets must be investigated, turned into one or more implementation-ready tickets, and driven through verified PRs. Do NOT use when one ticket is already implementation-ready; use ticket-to-pr instead. Do NOT use for ticket drafting without implementation; use ticket-writing instead.
Create or substantially revise editable bid and proposal slide decks, including implementing review feedback, from RFPs, source evidence, and reference decks. Use when evaluator alignment, requirement traceability, presentation narrative, native editability, and export-safe visual quality matter. Do not use for review-only requests or isolated typo fixes.
Use when an open GitHub PR must be monitored until the GitHub Codex bot gives an explicit LGTM reaction, rather than merely completing its review.
Use when a request names a unit of work and asks for it to be taken through several stages at once — "이 티켓 설계부터 PR까지", "take this issue through design, implementation and a PR", "이거 끝까지 해서 PR 올려줘". Do NOT use for a single-stage request (just fix this, just review this).
Use when a user asks to draft, create, file, rewrite, refine, or update a development ticket or issue in Notion, Jira, GitHub Issues, or another tracker, especially when another agent will implement from it.
Plugin manifests1
{
"name": "concord",
"version": "0.9.0-alpha.35",
"description": "Codex harness-engineering tools: session-state checkpoint, cross-session charter, review-until-green, review-until-lgtm, initiative-to-prs, provider-neutral ticket-writing, proposal-package-authoring, and ticket-to-pr.",
"author": {
"name": "arinyaho"
},
"license": "MIT",
"keywords": [
"review",
"review-until-lgtm",
"code-review",
"codex",
"harness",
"charter",
"session-state",
"ticket-writing",
"initiative-to-prs",
"ticket-to-pr",
"ticket"
],
"hooks": "./hooks.json"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[concord on Agent Plugins Marketplace](https://pluginsmp.com/plugins/concord-2)