codex-harness-javascript: Skill for Codex

.agents/skills/frontend-planning/SKILL.md

frontend-planning is a skill for Codex from thuandiep1707/codex-harness-javascript. It costs 57 tokens per session (508 once invoked), scanned A, original, MIT.

A planning workflow for turning frontend requirements into Jira work items: a Feature, functional Tasks, and specialist Subtasks. Jira is a project-tracking system, and the workflow stops before anyone starts coding or testing.

In plain words
What is it for?
Use it when a frontend request needs analysis, project-stack discovery, Jira decomposition, and verified work-item creation without dispatching design, coding, test-plan, or testing specialists.
Why use it?
It structures frontend work and keeps planning separate from implementation, while requiring the human-facing Jira content to be written in Vietnamese.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is thuandiep1707/codex-harness-javascript's own configuration. It tells Codex how to work on codex-harness-javascript itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything codex-harness-javascript configures →

Reuse

Borrowing it

Nothing to install: this file belongs to thuandiep1707/codex-harness-javascript. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/thuandiep1707/codex-harness-javascript/main/.agents/skills/frontend-planning/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/thuandiep1707/codex-harness-javascript

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for frontend-planning

README.md
[![agentmods](https://agentmods.dev/badge/skills/thuandiep1707/codex-harness-javascript/frontend-planning/github.svg)](https://agentmods.dev/skills/thuandiep1707/codex-harness-javascript/frontend-planning)
Your own site
<a href="https://agentmods.dev/skills/thuandiep1707/codex-harness-javascript/frontend-planning"><img src="https://agentmods.dev/badge/skills/thuandiep1707/codex-harness-javascript/frontend-planning/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for frontend-planning

Your own site · 80×15
<a href="https://agentmods.dev/skills/thuandiep1707/codex-harness-javascript/frontend-planning"><img src="https://agentmods.dev/badge/skills/thuandiep1707/codex-harness-javascript/frontend-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 508 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.00508
Opus 5.5 $0.00023 $0.00203
Sonnet 5.5 $0.00011 $0.00102
Haiku 4.5 $0.00006 $0.00051

Measured 1mo ago against content hash d0388febcaa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

frontend-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/frontend-planning/SKILL.md · 38 lines

How it starts

The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend Planning Workflow

This is a user-facing planning-only workflow. Main is the runtime Orchestrator.

Scrum Master planning and replan dispatches must use the operation-specific runtime profile defined by the Main orchestration contract in AGENTS.md.

Scope

  1. Main resolves the working product repository, execution intent plan-only, and current Jira-backed lifecycle entry.
  2. Main dispatches Brain for requirement analysis, authority readiness, and lightweight project-stack discovery when NEW or REPLAN requires it.
  3. Capture Brain result, close/verify Brain, and continue only when analysis-status: ready and authority.status: ready.
  4. Main dispatches Scrum Master with operation planning or replan, execution intent plan-only, and the approved analysis.
  5. Scrum Master discovers the current Jira project schema, resolves semantic work roles to actual Jira work types/fields/relationships, creates or reconciles the Jira work graph, and returns compact jira-work-report.
  6. Main closes/verifies Scrum Master and validates that the returned work graph is usable for later execution/resume.
  7. Stop before Design, Test Plan, Coding, Testing Logic, or Testing UI execution.

Planning rules

  • Decompose requirement -> user outcomes -> functional slices -> specialist execution units.
  • Treat work-container as optional grouping/context, not a required Jira issue type.
  • Resolve actual Jira work types, fields, options, relationships, and workflow states from the current project schema.
  • Do not split primarily by files, components, hooks, technical layers, or agent roles.
  • Human-facing Jira content must be Vietnamese; technical identifiers remain exact.
  • Detect project implementation stack from evidence; detection is not permission to adopt a new dependency.
  • Record unresolved technology/architecture decisions instead of defaulting to a library.
  • Main owns workflow/lifecycle decisions and child dispatch. Scrum Master alone owns Jira decomposition/schema-resolution/mutation for this workflow.

Read the full file on GitHub · 38 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago Changed · +2 lines d0388febcaa3
  2. 1mo ago Changed · +2 lines · +9 tokens per session 96066e1ba5d0
  3. 1mo ago Changed · -1 lines a36e23149a05
  4. 1mo ago Changed · +1 lines f94f3dc4f3ca
  5. 2mo ago First seen · 34 lines · 48 tokens per session scan A e1259fa09e2a

Subscribe to this mod's changes

frontend-planning is a skill published in the GitHub repository thuandiep1707/codex-harness-javascript (8 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 508 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

frontend-planning compared with skills from other repositories

frontend-planning next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
frontend-planningthuandiep1707/codex-harness-javascriptSkill81mo agoMITA57Codex
qaarcee-ai/nacSkill296yesterdayApache-2.0A131Codex
releasearcee-ai/nacSkill296yesterdayApache-2.0A53Codex
triagearcee-ai/nacSkill296yesterdayApache-2.0A65Codex
nac-onboardingarcee-ai/nacSkill296yesterdayApache-2.0C71Codex
verification-before-completionmvschwarz/openrigSkill8.7kyesterdayApache-2.0A26Claude Code, Codex
openrig-cmuxmvschwarz/openrigSkill8.7kyesterdayApache-2.0A122Claude Code, Codex