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.
npx skills add jxoesneon/Ciel --skill project-flow-opsgit clone --depth 1 https://github.com/jxoesneon/CielWrote 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.
[](https://agentmods.dev/skills/jxoesneon/ciel/project-flow-ops)<a href="https://agentmods.dev/skills/jxoesneon/ciel/project-flow-ops"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/project-flow-ops/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.
<a href="https://agentmods.dev/skills/jxoesneon/ciel/project-flow-ops"><img src="https://agentmods.dev/badge/skills/jxoesneon/ciel/project-flow-ops.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.00526 |
| Opus 5 | $0.00016 | $0.00263 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
project-flow-ops 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 8d 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.
What it actually says
CIEL ADAPTATION: Project Flow Ops (Backlog & Triage)
This skill manages the coordination between public surfaces (GitHub) and internal execution surfaces (Linear/Jira). It is used to rationalize backlogs and decide which items deserve active execution.
Classification Matrix
Every incoming issue or PR MUST be classified into one of these buckets:
- Merge: Self-contained, green CI, follows standards, ready for main.
- Port/Rebuild: Valuable logic/idea, but requires manual implementation via a CIEL sub-agent to ensure quality standards.
- Close: Out of scope, stale, unsafe, or redundant.
- Park: Valid but not prioritized for the current epic.
The Execution Bridge
- GitHub: Public truth and community feedback.
- Internal Tracker: Execution truth. Create an internal task ONLY if the work is scheduled, delegated, or requires cross-functional tracking.
Operational Rules
- Diff-First: Never classify a PR based on its description alone; the Orchestrator MUST read the full diff.
- CI Dependency: Do not mark an item as "Merge-Ready" if the CI is red.
- Product Alignment: If the real blocker is architectural or product direction, escalate to the human user rather than attempting to fix it with code.
Anti-Patterns
- Mechanical Mirroring: Creating an internal task for every trivial GitHub comment or "Thank You" issue.
- Blind Merging: Merging external PRs without a full CIEL security and quality audit.
- Notification Noise: Fanning out every minor issue update to multiple internal channels.
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.
- 8d ago First seen · 52 lines · 33 tokens per session scan A 76c271e53f4d
project-flow-ops is a skill published in the GitHub repository jxoesneon/Ciel (1 stars, last pushed 4d ago), licensed Apache-2.0. It adds 33 tokens to every session and 526 once invoked, about $0.0002 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.
Other skills, from other repositories
factory-handoff
Hand one exact agent-ready ticket to the central Factory runtime over the configured SSH forced-command boundary. Use when an operator asks to hand off an existing ticket or a prose request instead of implementing it in the current session.
proposal-filing
File a new Lorekeeper proposal ticket — create markdown, create GitHub issue, commit, push. Use when requesting a new feature, filing a bug, or submitting a product idea.
conductor-revert
Git-aware undo by logical work unit (track, phase, or task).
delivery
Fecha o ciclo de entrega local — build check, bump semântico, changelog e commit convencional. Deploy remoto somente sob a condição dupla do Ops. Use para "finalizar tarefa", "fazer release" ou "publicar versão".
feature-flow
Cria o diretório canônico da task (docs/todo/NNN-slug/), a branch e o scaffolding inicial. Use para "criar feature", "iniciar tarefa" ou "abrir task".
batonq-pr-runner
Implements a batonq task end-to-end and opens a pull request. Adds git discipline, branch naming, conventional-commit enforcement, and PR-body conventions on top of batonq-worker. Use when a task explicitly requires a PR (not a direct commit to main) — e.g., tasks running in fire-and-forget mode against repos with…