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 Benkapner/claude-code-basecamp --skill ci-guardgit clone --depth 1 https://github.com/Benkapner/claude-code-basecampWrote 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/benkapner/claude-code-basecamp/ci-guard)<a href="https://agentmods.dev/skills/benkapner/claude-code-basecamp/ci-guard"><img src="https://agentmods.dev/badge/skills/benkapner/claude-code-basecamp/ci-guard/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/benkapner/claude-code-basecamp/ci-guard"><img src="https://agentmods.dev/badge/skills/benkapner/claude-code-basecamp/ci-guard.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.00053 | $0.00849 |
| Opus 5.5 | $0.00021 | $0.00340 |
| Sonnet 5.5 | $0.00011 | $0.00170 |
| Haiku 4.5 | $0.00005 | $0.00085 |
Grade A, and why
ci-guard 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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI Guard
Repositories benefit from CI, but this skill is advisory. It checks for CI configuration and alerts when it is missing, while allowing research, prototypes, and intentionally local projects.
When to Activate
- At session start, after repository status is reported
- When a user clones or creates a new repo under
repositories/ - When running
/verifyor/quality-gatein a repo without CI
How to Check
Run the check script against any repo:
uv run skills/ci-guard/scripts/check-ci.py <repo-path>
The script checks for common CI indicators and the research exemption.
CI Indicators (any one is sufficient)
| Provider | Path |
|---|---|
| GitHub Actions | .github/workflows/ (with at least one .yml/.yaml) |
| GitLab CI | .gitlab-ci.yml |
| CircleCI | .circleci/config.yml |
| Jenkins | Jenkinsfile |
| Travis | .travis.yml |
| Azure | azure-pipelines.yml |
Research Exemption
A repo is exempt from the CI requirement if:
- A
.researchfile exists in the repo root, OR pyproject.tomlcontainspurpose = "research"in[project.optional]or as a comment marker
To mark a repo as research: touch <repo>/.research
Alert Behavior
When CI is missing and the repo is not research:
- Warn clearly at session start: "This repo has no CI configuration."
- Suggest a starter workflow based on the detected stack (Python/Node/Rust/Go)
- Reference the basecamp's own CI (
.github/workflows/ci.yml) as a working template - Do not block work - this is an alert, not a gate
Starter Templates
Python (uv-based, matching basecamp conventions)
name: CI
on:
pull_request:
branches: [main]
push:
branches: [main]
jobs:
lint:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/setup-uv@v6
- run: uv python install 3.12
- run: uv sync --group dev
- run: uv run ruff check .
- run: uv run ruff format --check .
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: astral-sh/setup-uv@v6
- run: uv python install 3.12
- run: uv sync --group dev
- run: uv run pytest -v
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.
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.
- 1mo ago Changed fb60d4a0d476
- 1mo ago First seen · 119 lines · 53 tokens per session scan A df381d3e8fa8
ci-guard is a skill published in the GitHub repository Benkapner/claude-code-basecamp (17 stars, last pushed 15d ago), licensed MIT. It adds 53 tokens to every session and 849 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-cloud-slo-alert-configuration
Configures Cloud Monitoring PromQL-based Service Level Objective (SLO) alerting policies on Google Cloud for resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
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.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
factory
Experimental workflow for configuring an autonomous software delivery factory. Use when choosing feedback sources, schedules, worktree behavior, autonomy gates, or host automations.