init-project-orchestration

init-project-orchestration is a skill for Claude Code, Codex from flonat/flonat-research. It costs 77 tokens per session (1,362 once invoked), scanned A, original, MIT.

A project setup tool for defining shared AI agents, repeatable workflows, and planning files from one common configuration.

In plain words
What is it for?
Use it to organise research-project roles, commands, phase tracking, and roadmap state across both coding assistants.
Why use it?
It avoids maintaining separate, potentially inconsistent instructions for Claude Code and Codex.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions Claude Code.

Good fit Use it to organise research-project roles, commands, phase tracking, and roadmap state across both coding assistants.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/flonat/flonat-research/init-project-orchestration
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add flonat/flonat-research --skill init-project-orchestration
Clone the repo
git clone --depth 1 https://github.com/flonat/flonat-research

Made for: Claude Code, 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 init-project-orchestration

README.md
[![agentmods](https://agentmods.dev/badge/skills/flonat/flonat-research/init-project-orchestration/github.svg)](https://agentmods.dev/skills/flonat/flonat-research/init-project-orchestration)
Your own site
<a href="https://agentmods.dev/skills/flonat/flonat-research/init-project-orchestration"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/init-project-orchestration/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 init-project-orchestration

Your own site · 80×15
<a href="https://agentmods.dev/skills/flonat/flonat-research/init-project-orchestration"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/init-project-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,362 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00077 $0.01362
Opus 5 $0.00039 $0.00681
Sonnet 5 $0.00015 $0.00272
Haiku 4.5 $0.00008 $0.00136

Measured 6d ago against content hash 7febc9db94b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

init-project-orchestration 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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/project-orchestration.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/init-project-orchestration/SKILL.md · 155 lines

How it starts

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

Initialize project orchestration

Create the project source once under .ai/orchestration/. Treat Claude Code and Codex files as generated adapters, never as parallel authoring surfaces.

Resulting structure

.ai/orchestration/                 # canonical, client-neutral source
├── manifest.yaml
├── agents/<role>.md
└── commands/<workflow>.md

.claude/agents/project-<role>.md   # generated Claude agent
.claude/commands/project/<workflow>.md
.codex/agents/project-<role>.toml  # generated Codex agent
.agents/skills/project-<workflow>/SKILL.md
.planning/roadmap.md               # shared project state
.planning/state.md

Claude exposes a workflow as /project:<workflow>. Codex exposes the same workflow as $project-<workflow>. Both adapters derive from the same neutral command body. The namespace prevents collisions with global skills.

Phase 1: Assess

  1. Resolve the project root from the argument or current directory. Confirm it is the intended research project before searching elsewhere.
  2. Read the active client's project guidance. Read neutral project facts from AI.md, README.md, docs/, and .context/; do not treat the sibling client's guidance file as an additional instruction set.
  3. Read .context/field-calibration.md, project memory, and .planning/ when present.
  4. Classify the project:
    • experimental: data preparation and empirical estimation;
    • computational: software, algorithms, simulations, or experiments;
    • theoretical: formal models and proofs;
    • mixed: select roles and workflows from more than one preset.
  5. Inventory existing neutral sources and generated adapters. Also inventory legacy non-generated .claude/agents/ and .claude/commands/ files.

Do not overwrite anything during assessment.

Phase 2: Confirm the design

Read the applicable preset under templates/presets/ and present:

  • proposed project agents and their exact read/write boundaries;
  • proposed project workflows and expected arguments;
  • the initial .planning/ phases;
  • any legacy single-client Claude files that need reconciliation.

Read the full file on GitHub · 155 lines

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. 6d ago First seen · 155 lines · 77 tokens per session scan A 7febc9db94b2

Subscribe to this mod's changes

init-project-orchestration is a skill published in the GitHub repository flonat/flonat-research (132 stars, last pushed 14d ago), licensed MIT. It adds 77 tokens to every session and 1,362 once invoked, about $0.0004 per session on Opus 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-09-03.