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 tomzx/agents --skill configure-labelsgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/configure-labels)<a href="https://agentmods.dev/skills/tomzx/agents/configure-labels"><img src="https://agentmods.dev/badge/skills/tomzx/agents/configure-labels/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/tomzx/agents/configure-labels"><img src="https://agentmods.dev/badge/skills/tomzx/agents/configure-labels.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.02272 |
| Opus 5.5 | $0.00012 | $0.00909 |
| Sonnet 5.5 | $0.00006 | $0.00454 |
| Haiku 4.5 | $0.00003 | $0.00227 |
Grade A, and why
configure-labels 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 22d 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.
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure Repository Labels
Sets up the standard label taxonomy in a GitHub repository so that downstream skills (triage-issues, label-issue, prioritize-issues) can classify and manage issues consistently. Creates missing labels, updates descriptions and colors for existing labels that do not match the convention, and removes conflicts with GitHub defaults. Idempotent: safe to re-run on a repository that already has some or all labels configured.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, operate on
$REPO. ghCLI authenticated with write access to the target repository- Repository in
owner/repoformat ($1), or omit to use the repository in the current working directory
Workflow
Determine target repository ($1 or CWD)
|
v
Fetch existing labels via gh label list
|
v
Compute desired label set (standard + project-specific)
|
v
For each desired label:
Exists?
/ \
Yes No
| |
v v
Update if Create label
name/color/ via gh label
desc differ
| |
+-----+-----+
|
v
Report: created, updated, unchanged, conflicts
Standard Label Taxonomy
The label set is organized into dimensional namespaces. Every SDLC-managed repository should have labels from the dimensions that are relevant to its domain.
Type Labels
| Name | Color | Description |
|---|---|---|
bug |
d73a4a |
Something isn't working |
feature |
0075ca |
New feature or request |
question |
d876e3 |
Further information is requested |
chore |
fef2c0 |
Maintenance, refactoring, or dependency updates |
documentation |
0075ca |
Improvements or additions to documentation |
security |
b60205 |
Vulnerability or security concern |
Area Labels
Area labels use the area: prefix.
Do not create the full catalog blindly.
Instead, derive the project's areas from its structure and context files (see "Area Discovery" below).
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.
- 22d ago Changed · -1 lines 7af42638ec09
- 2mo ago First seen · 235 lines · 30 tokens per session scan A cc122adc6b96
configure-labels is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 2,272 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.