kendex: Skill for Claude Code

.agents/skills/github-repository-settings/SKILL.md

github-repository-settings is a skill for Claude Code from vanillagreencom/kendex. It costs 24 tokens per session (725 once invoked), scanned C, original, MIT.

A set of tools for previewing, generating, and checking selected GitHub repository instruction and review files. GitHub is a service that hosts code repositories, and these files tell automated tools how to handle a project.

In plain words
What is it for?
It helps preview a takeover of settings, render selected outputs, check working or staged files, and report whether they match the expected configuration.
Why use it?
It helps keep generated repository settings consistent and detects differences without immediately changing files. A preview mode shows what would be adopted before anything is written.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: installed under .agents/ (shared by several agents); mentions Codex.

This is vanillagreencom/kendex's own configuration. It tells Claude Code how to work on kendex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kendex configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vanillagreencom/kendex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/vanillagreencom/kendex/main/.agents/skills/github-repository-settings/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/vanillagreencom/kendex

Made for: Claude Code.

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 github-repository-settings

README.md
[![agentmods](https://agentmods.dev/badge/skills/vanillagreencom/kendex/github-repository-settings/github.svg)](https://agentmods.dev/skills/vanillagreencom/kendex/github-repository-settings)
Your own site
<a href="https://agentmods.dev/skills/vanillagreencom/kendex/github-repository-settings"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/github-repository-settings/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 github-repository-settings

Your own site · 80×15
<a href="https://agentmods.dev/skills/vanillagreencom/kendex/github-repository-settings"><img src="https://agentmods.dev/badge/skills/vanillagreencom/kendex/github-repository-settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 725 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00024 $0.00725
Opus 5.5 $0.00010 $0.00290
Sonnet 5.5 $0.00005 $0.00145
Haiku 4.5 $0.00002 $0.00072

Measured 3d ago against content hash b574ec0bd94b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

github-repository-settings scanned grade C with 1 finding 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 3d 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

<!-- kendex:project-instructions:start -->
.agents/skills/github-repository-settings/SKILL.md · 43 lines

How it starts

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

Project Instructions

Problems with a kendex-owned skill go through kendex report; check ownership in the file first.

GitHub repository settings

.agents/skills/github-repository-settings/scripts/github-repository-settings adopt --dry-run
.agents/skills/github-repository-settings/scripts/github-repository-settings render
.agents/skills/github-repository-settings/scripts/github-repository-settings check
.agents/skills/github-repository-settings/scripts/github-repository-settings check --staged

Use adopt --dry-run to preview takeover without writes. Keep the existing bot-instructions manifest. The library reports hand edits and refuses symlinked preview targets. render writes the selected outputs. check compares them without writes. check --staged reads tracked settings and review files from the index. Process and private-file settings keep their working values and normal precedence. A nested settings file keeps its working values only when it is absent from HEAD and the index. A staged deletion stays absent even if its working file remains. Exit codes: 0 clean, 1 findings, 2 could not complete. Options and the check report contract: scripts/github-repository-settings --help.

Preview grants no write ownership. Use the existing bot-instructions adoption operation to take unmanaged content over before rendering it.

Before adoption, choose hosted or local for GITHUB_STANDARD_CHECK_LOCATION in the settings [env] table. It has no default. When both adoption keys are empty or absent, check reports not adopted and exits 0 without judging review files. This package reports the value during check; it installs no hosted CI. GITHUB_STANDARD_BOT_REVIEW defaults to off. Off selects the library's local output. On selects its full output and the bots enabled in the manifest. Local output requires the manifest's codex flag and an installed bot-instructions package inside the checkout. The settings example declares the settings.

Read the full file on GitHub · 43 lines

Files

What ships with it

3 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. 3d ago Changed b574ec0bd94b
  2. 10d ago First seen · 43 lines · 24 tokens per session scan C e2895062ac7d

Subscribe to this mod's changes

github-repository-settings is a skill published in the GitHub repository vanillagreencom/kendex (87 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 725 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-19.

Related

Other skills, from other repositories

rp

Always read this skill when the user mentions "rp" or "repoprompt", or before accessing a repository outside the current RepoPrompt workspace. Covers workspace discovery, binding, root verification, and workspace hygiene.

w-winter/dot314 · 44 tokens

prose-review

Review prose written for others (e.g., user-facing documentation, prompts for other LLMs, reports, plans, inline comments, docstrings) for local jargon leakage, orphaned references, missing grounding, and audience or genre mismatch. Always run on prose you produce or materially edit, except for routine conversational…

w-winter/dot314 · 84 tokens

text-search

Search indexed text corpora with qmd. For indexed content, prefer qmd over grep.

w-winter/dot314 · 22 tokens

commit

A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.

mrclrchtr/supi · 7 tokens

work-on-ticket

Fetches Jira ticket details, creates an appropriately named branch, and initiates the task planning workflow. Use when the user says "work on [TICKETID]" or similar phrases.

jjmartres/ai-coding-agents · 41 tokens

linear-tracker

Resolve project-local issue tracker routing and publish Linear issues safely. Use before creating Linear issues, PRDs, phase breakdown issues, or when deciding whether Linear/GitHub/local docs is the configured tracker. Enforces capability ≠ routing: Linear requires project-local policy, team association, auth, and…

joelhooks/pi-tools · 67 tokens