add-project

A setup skill that adds a virtual project to a dev-loop workspace and synchronizes it with the team's backend. Dev-loop is a system where software agents coordinate development work through tickets.

In plain words
What is it for?
Creating or finding a Linear or local-hub project, setting its labels, preparing its strategy document, and saving the project configuration.
Why use it?
It keeps the local project configuration and backend project aligned when a new product area is introduced.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/dyzsasd/dev-loop/add-project
Any agent
npx skills add dyzsasd/dev-loop --skill add-project
Clone the repo
git clone --depth 1 https://github.com/dyzsasd/dev-loop

Made for: Claude Code, Codex.

Per session 146 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,187 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00146 $0.01187
Opus 5 $0.00073 $0.00593
Sonnet 5 $0.00029 $0.00237
Haiku 4.5 $0.00015 $0.00119

Measured 2d ago against content hash 49eb0af2618c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

add-project 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 2d 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.

skills/add-project/SKILL.md · 91 lines

How it starts

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

add-project — register a virtual project + backend sync

ROLE: You are the operator-present setup skill that creates a workspace project AND aligns it with the backend in the same pass, so config and backend never drift.

MISSION

A project is a virtual unit (a Linear/hub project + delivery semantics) that later references repos (workspace model, §27). This skill interviews the operator, find-or-creates the backend project, ensures the label taxonomy, scaffolds the strategy doc, and persists the project through the validated mutator. Repos are added separately with /dev-loop:add-repo.

BOOT

Operator-present, but each invocation is fresh (§0); boot per §0a (the Topology block + the sections cited below). Inputs:

  • The workspace dev-loop.json, resolved from cwd — none ⇒ tell the user to dev-loop team init first and stop.
  • references/config-schema.md (the field shapes the mutator writes). Sections: §0 §0a §2 §4 §5a §9c §20 §27

JOBS

1. INTERVIEW

  • key — a lowercase project key (state-dir + config key; not a reserved name): the workspace-internal handle.
  • linearProject / hub project name — the human name in the backend.
  • testEnv (base URL + any auth constraint), devSplit (two-tier senior/junior dev?), optional per-agent launch overrides.
  • intake.mode (§5a): autonomous (default — PM proactively reviews the product and files its own work) or passive (PM only responds to explicit needs-pm intake; nothing is originated). Passive suits maintenance projects or teams where a human owns the roadmap; a passive project may skip the strategy doc.
  • blockedStateName — did the operator add a real "Blocked" column in Linear? Record its name; else leave null (the blocked label park applies). Do not skip silently.
  • comms — confirm team.comms is set (or explicitly declined); without it human-park pings and digests have no channel.

2. BACKEND SYNC (the reason this is a coding-CLI skill, not pure CLI)

Read the full file on GitHub · 91 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. 2d ago First seen · 91 lines · 146 tokens per session scan A 49eb0af2618c

Subscribe to this mod's changes

add-project is a skill published in the GitHub repository dyzsasd/dev-loop (5 stars, last pushed 4d ago), licensed MIT. It adds 146 tokens to every session and 1,187 once invoked, about $0.0007 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens