Mole Bug Patterns
tw93/Mole
A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
Install Add Repo Operation
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install agntcy/coffeeAgntcy add-repo-operation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .claude/skills/add-repo-operation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .claude/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install agntcy/coffeeAgntcy add-repo-operation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .agents/skills/add-repo-operation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .agents/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install agntcy/coffeeAgntcy add-repo-operation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .cursor/skills/add-repo-operation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .cursor/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/agntcy/coffeeAgntcy.git --path .agents/skills/repo-tooling/add-repo-operation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install agntcy/coffeeAgntcy add-repo-operation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .gemini/skills/add-repo-operation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .gemini/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install agntcy/coffeeAgntcy add-repo-operationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .github/skills/add-repo-operation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .github/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install agntcy/coffeeAgntcy add-repo-operation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/agntcy/coffeeAgntcy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/repo-tooling/add-repo-operation .opencode/skills/add-repo-operation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "add-repo-operation" agent skill from https://github.com/agntcy/coffeeAgntcy/tree/main/.agents/skills/repo-tooling/add-repo-operation into .opencode/skills/add-repo-operation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "add-repo-operation", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
add-repo-operation- GitHub stars
- 112
- Token cost
- ~1.1k tokens
- SKILL.md length
- 201 words
- Files
- 1
- Skills in repo
- 20
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
- Asked to add a new check
- SKILL.md covers When to use, Reference example, Steps and After adding it, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Tool to this repo
What it does
Add Repo Operation is an agent skill from agntcy/coffeeAgntcy. Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline. Use when asked to add a new check, validation, or tool to this repo, or to audit whether an existing one is complete.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development. It works with Bash. The repository describes itself as: End-to-end reference application for AGNTCY Components. The licence is Apache-2.0.
When your agent uses it
- Asked to add a new check
- Tool to this repo
- Audit whether an existing one is complete
Example prompts
- “Use the add-repo-operation skill to guide adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard…”
- “/add-repo-operation”
What it can do on your machine
Read from SKILL.md and the folder at commit 78f588c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Add Repo Operation loads about 1.1k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 201 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from agntcy/coffeeAgntcy at commit 78f588c, republished under its Apache-2.0 licence (© agntcy). 201 words, ~1,101 tokens.
Download SKILL.mdSave it as
.claude/skills/add-repo-operation/SKILL.md (or your agent's skills folder).- name
- add-repo-operation
- description
- Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script -> Taskfile task -> skill -> CI enforcement -> rule pipeline. Use when asked to add a new check, validation, or tool to this repo, or to audit whether an existing one is complete.
Add a repository operation
When to use
Whenever asked to add a new check, validation, or piece of tooling to this
repo, or to audit whether an existing one already follows the pipeline in
.agents/rules/meta/repo-operation-pipeline.md.
Reference example
Use shell script linting as the concrete template to copy the shape of - it has every layer:
| Layer | Shell-linting's version |
|---|---|
| Script | scripts/lint/lint_shell.bash |
| Taskfile task | shell:lint / shell:fmt in Taskfile.yaml |
| Skill | .agents/skills/quality-checks/linting-shell-scripts/SKILL.md |
| CI enforcement | One of the parallel checks in scripts/checks/check_all.bash, run via task check:all in .github/workflows/checks.yaml |
| Rule | .agents/rules/quality/shell-script-linting.md |
<!-- alphabetize-exempt: layers are the pipeline in execution order (script, task, skill, CI, rule) -->Steps
- [ ] 1. Write the script under scripts/<category>/ as scripts/<category>/<name>.bash (an existing category like checks/ or lint/ if it fits, a new one if it doesn't - or scripts/lib/ for a shared helper) - resolve any tool it needs via .tools/bin first, falling back to PATH (see lint_shell.bash's resolve_tool for the pattern).
- [ ] 2. Add a Taskfile task that wraps it and nothing else.
- [ ] 3. Add a skill under .agents/skills/<category>/<name>/SKILL.md (an existing category like quality-checks/ or repo-tooling/ if it fits, a new one if it doesn't) that points an agent at the task, not the script.
- [ ] 4. If it's a check/invariant (not a one-shot generative action): add it to scripts/checks/check_all.bash's parallel list, so `task check:all` and the "Checks" CI workflow both pick it up with no other file needing to change - this applies to a workflow-file check too, since ci-gate.yaml runs no check of its own (only waits for and summarizes sibling runs, checks.yaml included). Only give it its own workflow file if it has a genuinely different execution model (see "Known exceptions" in the rule) - ci-gate.yaml waits on any such new workflow automatically, no manual list to update there either.
- [ ] 5. Add a rule under .agents/rules/<category>/<name>.md (an existing category if it fits, a new one if it doesn't) documenting the convention and cross-linking the other four layers, then index both the skill and the rule in AGENTS.md's tables (alphabetized within their section - see .agents/rules/formatting/alphabetize-entity-lists.md and .agents/rules/formatting/organize-large-collections.md for choosing/growing a category).
- [ ] 6. Add a row to .agents/rules/always-apply/pre-finalize-checks.md if it's a check.After adding it
- [ ] 1. Run the new task directly to confirm it works: task <name>
- [ ] 2. Run task shell:lint if you added or changed a script.
- [ ] 3. Run task workflows:lint if you added or changed a workflow file.
- [ ] 4. Run task check:all to confirm it runs alongside everything else without breaking the parallel run.
- [ ] 5. If it landed in checks.yaml, actionlint the changed workflow file and confirm the job's bootstrap + task invocation actually runs clean locally first.Rules
- Default to folding a new check into
scripts/checks/check_all.bash, not a new workflow file - that's what keepschecks.yamla single bootstrap plus a single parallel run instead of drifting back into one workflow per check. - Don't force a dedicated workflow file onto something that fits one of the existing ones just because it feels more "official."
- Don't force CI enforcement of any kind onto a purely generative, one-shot action (e.g. a tooling version bump - see
manage-repo-tooling) - there's nothing standing left to check once it's run. - When something looks like it should skip a layer, name which exception category it falls under (see "Known exceptions" in
.agents/rules/meta/repo-operation-pipeline.md) rather than silently doing a partial job.
© agntcy, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .agents/skills/repo-tooling/add-repo-operation of agntcy/coffeeAgntcy.
Open the folder on GitHubat commit 78f588c
Compare with similar skills
Add Repo Operation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Add Repo Operation this skillagntcy/coffeeAgntcy | 112 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Mole Bug Patternstw93/Mole | 70k | — | ~2k | Automated safety check: Pass | GPL-3.0 | |
| Segment CreateJanDeDobbeleer/oh-my-posh | 24k | — | ~660 | Automated safety check: Pass | MIT | |
| CLI DeveloperJeffallan/claude-skills | 12k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| JSON Processing with jqcharmbracelet/crush | 29k | — | ~746 | Automated safety check: Pass | Custom licence | |
| Omm Pushoh-my-mermaid/oh-my-mermaid | 2.7k | — | ~441 | Automated safety check: Pass | MIT |
Similar skills
Segment Create
JanDeDobbeleer/oh-my-posh
Checklist for adding a new Oh My Posh segment. An agent skill from JanDeDobbeleer/oh-my-posh.
CLI Developer
Jeffallan/claude-skills
Walks through designing, building and polishing a command-line tool: user workflow and command hierarchy, implementation in commander, click, typer or cobra, completions and cross-platform testing.
JSON Processing with jq
charmbracelet/crush
Explains the jq command built into Crush for querying, filtering and reshaping JSON, including its supported flags and where it differs from standard jq.
Omm Push
oh-my-mermaid/oh-my-mermaid
Push architecture docs to oh-my-mermaid cloud. An agent skill from oh-my-mermaid/oh-my-mermaid.
Golang
JanDeDobbeleer/oh-my-posh
Go conventions for this project that differ from common Go practice.
More from agntcy/coffeeAgntcy
All 20 skills in this repoA2a Protocol
agntcy/coffeeAgntcy
A skill your agent uses when the user asks about A2A (Agent-to-Agent) protocol communication, OASF record formats, AGNTCY directory operations, agent card parsing, or dirctl CLI usage.
Agentic Workflows API Documentation Lungo
agntcy/coffeeAgntcy
Authors and maintains the human-facing Agentic Workflows API documentation for the lungo subproject at coffeeAGNTCY/coffeeagents/lungo/docs/workflow-instanceapi.md.
Checking Helm Chart Version Bumps
agntcy/coffeeAgntcy
Checks whether any Helm chart under coffeeAGNTCY/coffeeagents/{corto,lungo}/deployment/helm// has content changes not covered by a later Chart.yaml version: bump, anywhere in that chart's history…
Checking Pinned References
agntcy/coffeeAgntcy
Runs task pins:check to find any third-party GitHub Action, reusable-workflow, or image reference that isn't pinned to an immutable SHA/digest, and pins each one it finds.
Checking Workflow Permissions
agntcy/coffeeAgntcy
Runs task workflows:check-permissions to find any GitHub Actions workflow file with a write-all grant or no declared permissions, and scopes it down to least privilege.
Generate Release Notes
agntcy/coffeeAgntcy
Generates coffeeAgntcy CHANGELOG release notes and README Built With updates from PRs and dependency lockfiles since the previous release tag.
Related
Works with
Categories
Questions about Add Repo Operation
What does Add Repo Operation do?
Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline. Add Repo Operation is an agent skill from agntcy/coffeeAgntcy. Guides adding a new repository operation (a check, validation, or piece of tooling) through this repo's standard script - Taskfile task - skill - CI enforcement - rule pipeline.
When should I use Add Repo Operation?
Add Repo Operation fits situations like: asked to add a new check; tool to this repo; audit whether an existing one is complete.
How do I install Add Repo Operation in Claude Code?
Run `npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a claude-code`. Or copy the skill folder (.agents/skills/repo-tooling/add-repo-operation in agntcy/coffeeAgntcy) into .claude/skills/add-repo-operation in your project. Claude Code loads it when a task matches its description.
How do I install Add Repo Operation in Codex?
Run `npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a codex`. Or copy the skill folder (.agents/skills/repo-tooling/add-repo-operation in agntcy/coffeeAgntcy) into .agents/skills/add-repo-operation in your project. Codex loads it when a task matches its description.
Can I use Add Repo Operation in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add agntcy/coffeeAgntcy --skill add-repo-operation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-repo-operation, .gemini/skills/add-repo-operation, .github/skills/add-repo-operation and .opencode/skills/add-repo-operation in your project.
What does Add Repo Operation need to run?
SKILL.md names no scripts, command-line tools or credentials: Add Repo Operation is instructions for the agent only.
Does Add Repo Operation access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Add Repo Operation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Add Repo Operation use?
Add Repo Operation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Add Repo Operation use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Add Repo Operation?
Skills that share tags, products or a category with Add Repo Operation: Mole Bug Patterns (tw93/Mole, 70k stars), Segment Create (JanDeDobbeleer/oh-my-posh, 24k stars), CLI Developer (Jeffallan/claude-skills, 12k stars) and JSON Processing with jq (charmbracelet/crush, 29k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Add Repo Operation?
agntcy (a GitHub organization) maintains it in agntcy/coffeeAgntcy, which has 112 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 9, 2026.
Source: agntcy/coffeeAgntcy on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.