repo-guidance-sync

repo-guidance-sync is a skill for Codex from Agent-Hellboy/mcp-runtime. It costs 117 tokens per session (1,098 once invoked), scanned A, original, Apache-2.0.

A documentation review and update workflow for software repositories. It checks whether guides, contributor instructions, runbooks, and test guidance match the code, commands, configuration, and operational behaviour.

In plain words
What is it for?
Use it after code, UI, CLI, API, configuration, deployment, or test changes to find affected documentation and update the appropriate files.
Why use it?
It prevents documentation from describing outdated setup steps, interfaces, tests, or deployment and troubleshooting procedures.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: mentions AGENTS.md.

Good fit Use it after code, UI, CLI, API, configuration, deployment, or test changes to find affected documentation and update the appropriate files.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/agent-hellboy/mcp-runtime/repo-guidance-sync
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 Agent-Hellboy/mcp-runtime --skill repo-guidance-sync
Clone the repo
git clone --depth 1 https://github.com/Agent-Hellboy/mcp-runtime

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 repo-guidance-sync

README.md
[![agentmods](https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/repo-guidance-sync/github.svg)](https://agentmods.dev/skills/agent-hellboy/mcp-runtime/repo-guidance-sync)
Your own site
<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/repo-guidance-sync"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/repo-guidance-sync/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 repo-guidance-sync

Your own site · 80×15
<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/repo-guidance-sync"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/repo-guidance-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 117 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,098 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.00117 $0.01098
Opus 5 $0.00059 $0.00549
Sonnet 5 $0.00023 $0.00220
Haiku 4.5 $0.00012 $0.00110

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

Security

Grade A, and why

repo-guidance-sync 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.

.codex/skills/repo-guidance-sync/SKILL.md · 62 lines

How it starts

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

Repo Guidance Sync

Overview

Use this skill to decide what documentation must change after a code, design, or product update, then make those edits in the right files with verifiable links back to source behavior.

If the user asks for a doc-sync audit and no files need changes, say that clearly and cite the source files or searches checked.

Workflow

  1. Identify the change surface.

    • Inspect the diff, touched packages, new commands, config flags, UI behavior, API shapes, CRDs, generated schemas, deployment manifests, and tests.
    • If the change affects setup, CLI workflows, operator reconciliation, ingress/gateway behavior, auth/policy, registry/image handling, observability, or cache-mode assumptions, identify the matching E2E scenario in test/e2e/kind.sh or adjacent integration tests before editing docs.
    • Search for existing docs before adding new files: rg -n "<command|field|feature|concept>" README.md AGENTS.md docs website config api internal services.
    • Prefer updating the nearest existing guide, reference, or runbook over creating a new document.
  2. Classify required doc updates.

    • User-facing product change: update README, docs guides, CLI examples, API/reference pages, screenshots or UI copy references if present.
    • Developer workflow change: update AGENTS.md, build/test instructions, local setup notes, failure modes, environment variables, or repo map entries.
    • Codebase architecture or contributor-flow change: review docs/internals/ and decide whether the overview, package tours, or Mermaid diagrams need updates. Add or revise diagrams only when they clarify package boundaries, request flow, reconciliation flow, service interactions, or contributor decision points.
    • Design change: update design-system rules, component guidance, UX behavior notes, or docs that describe screens/workflows.
    • Operational change: update install, deployment, TLS, registry, Kubernetes, observability, and rollback/debug instructions.
    • Schema/contract change: update CRD/API docs, examples, generated docs if the repo owns them, and any golden snapshots tied to CLI help.
    • E2E-visible behavior change: update or add the relevant E2E assertion in test/e2e/kind.sh when the behavior is exercised through Kind, real MCP traffic, policy/session state, OAuth, observability, registry/image paths, or cluster doctor. If narrower unit/integration coverage is sufficient, note why in the final validation summary.

Read the full file on GitHub · 62 lines

Files

What ships with it

4 files 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. 8d ago First seen · 62 lines · 117 tokens per session scan A ccc0a3ae4430

Subscribe to this mod's changes

repo-guidance-sync is a skill published in the GitHub repository Agent-Hellboy/mcp-runtime (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 117 tokens to every session and 1,098 once invoked, about $0.0006 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

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

baoyu-youtube-transcript

A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.

JimLiu/baoyu-skills · 107 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

read

Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…

tw93/Waza · 78 tokens

overleaf-sync

A two-way connection between a local paper folder and Overleaf, a web-based LaTeX editor for writing research papers. It lets you move changes between the local files and the shared Overleaf project.

wanshuiyin/Auto-claude-code-research-in-sleep · 97 tokens

pdf-verification-cli

Verify PDF page count and content using command-line tools when Python libraries unavailable.

HKUDS/OpenSpace · 19 tokens