What is dev-repo-readiness?

A repository-readiness checker for a local code project, comparing it with its remote version, continuous-integration results, contributors, and public profile. It preserves the evidence and records how the check was performed.

Use it before sharing or publishing a repository to inspect remote state, CI, contributors, and public project context. It also supports documented execution phases and trace files.

It helps reveal whether the local project matches the remote one and whether its automated checks and public-facing information are in good shape. The recorded evidence makes the conclusions easier to review.

dev-repo-readiness — Skill for Claude Code and Codex by modiqo

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 modiqo/skillspec --skill repo-readiness

Clone the repo

git clone --depth 1 https://github.com/modiqo/skillspec

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/modiqo/skillspec/repo-readiness/github.svg)](https://agentmods.dev/skills/modiqo/skillspec/repo-readiness)

Your own site

<a href="https://agentmods.dev/skills/modiqo/skillspec/repo-readiness"><img src="https://agentmods.dev/badge/skills/modiqo/skillspec/repo-readiness/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/modiqo/skillspec/repo-readiness"><img src="https://agentmods.dev/badge/skills/modiqo/skillspec/repo-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,734 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 88% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00050	$0.02734
Opus 5	$0.00025	$0.01367
Sonnet 5	$0.00010	$0.00547
Haiku 4.5	$0.00005	$0.00273

Measured 11d ago against content hash 544c2952eecd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

dev-repo-readiness 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 11d 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.

Origin

This is a copy

88% identical to generic-skill-creator — 26 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

examples/repo-readiness/SKILL.md · 122 lines

How it starts

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

repo readiness

Check a local repository against remote state, CI, contributors, and public profile context.

This skill is a thin loader for the colocated skill.spec.yml. The spec is the source of truth for routes, rules, dependencies, imports, resources, recipes, tests, and trace requirements. Do not treat the spec as background prose; treat it as the execution contract for this task.

Runtime Contract

Load ./skill.spec.yml from this skill folder before taking task actions.
When the skillspec CLI is available and the spec shape is unfamiliar, run skillspec sensemake ./skill.spec.yml --view index to learn the section roles, counts, query handles, and navigation grammar without dumping the full YAML.

Then create the ordered phase plan and current-route action checklist:

skillspec plan ./skill.spec.yml --input='<user task>' --trace-dir "${PWD}/.skillspec/traces"
skillspec act ./skill.spec.yml --input='<user task>' --run <run_dir> --phase <phase-id>

Strip skill invocation prefixes such as /my-skill, $my-skill, or /durable-executor-spec before passing --input.
Preserve the emitted trace run_dir.
Read the full phase plan and action checklist before using tools. Treat them as the active execution SOP, not as advice. The PHASE TOOL BOUNDARY - HARD section is the permission boundary for the next action.
For each execution phase, run skillspec act ./skill.spec.yml --input='<user task>' --run <run_dir> --phase <phase-id> before acting, record phase progress in <run_dir>/execution.jsonl, then run skillspec progress show ./skill.spec.yml --run <run_dir> to see completed, current, blocked, and remaining phases.
Pull active details with skillspec query ./skill.spec.yml <handle> --view summary and relationship edges with skillspec refs ./skill.spec.yml <handle> --view summary. Prefer precise handles such as rule:<id>, rule:<id>.forbid, command:<id>.requires, and state:<id>.next over reading the whole spec.
Before every substrate/tool call, apply the phase tool boundary and checklist allow/deny questions. Any unlisted tool, data source, execution substrate, provider, adapter, CLI, browser mode, API, or skill requires explicit user permission before use. The selected route and matched rules override lower-level skill defaults and generic tool preferences.
When the CLI is available after a trace exists, run skillspec trace align ./skill.spec.yml --decision-trace <run_dir> and, when structured action evidence exists, add --execution-trace <run_dir>/execution.jsonl. The command writes <run_dir>/alignment.json; report the alignment status, meaning, model layers, evidence gaps, user-facing proof rows, summary, and trace path.
If skillspec plan, skillspec act, or skillspec progress is unavailable, fall back to skillspec decide, then manually construct the same ordered phase checklist and progress notes before using tools. If the CLI is unavailable, read skill.spec.yml directly and apply the same contract manually. Do not expand this loader into a second source of truth.

Read the full file on GitHub · 122 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.

skill.spec.yml 5.9 KB

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.

11d ago First seen · 122 lines · 50 tokens per session scan A 544c2952eecd

Subscribe to this mod's changes

dev-repo-readiness is a skill published in the GitHub repository modiqo/skillspec (741 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,734 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to generic-skill-creator, differing in 26 lines, and is treated as a copy.

CI and CD DevOps and cloud Git and workflow ai ai-agents ai-evals ai-tool

chinese-git-workflow

A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.

jnMetaCode/superpowers-zh · 69 tokens

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

atmos-hooks

Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.

cloudposse/atmos · 46 tokens

atmos-pro

Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.

cloudposse/atmos · 38 tokens

start-temps-cluster

Start (or restart) a local multi-node Temps cluster using Docker-in-Docker — one control plane + 3 worker nodes, each a privileged DinD container running its own dockerd + temps agent, wired with the real multi-host overlay (VXLAN, computecidr allocation) via tools/dev-cluster/ in whichever checkout/worktree you run…

gotempsh/temps · 204 tokens

pr-watch

Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.

SethGammon/Citadel · 46 tokens