Borrowing it
Nothing to install: this file belongs to avivsinai/jenkins-cli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/avivsinai/jenkins-cli/main/CLAUDE.mdgit clone --depth 1 https://github.com/avivsinai/jenkins-cliWrote 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/instructions/avivsinai/jenkins-cli/claude-md)<a href="https://agentmods.dev/instructions/avivsinai/jenkins-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/avivsinai/jenkins-cli/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.01057 | $0.01057 |
| Opus 5 | $0.00528 | $0.00528 |
| Sonnet 5 | $0.00211 | $0.00211 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
jenkins-cli CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This is the master agent instruction file for this repository. Keep repository policy here. AGENTS.md exists only as a Codex compatibility shim and should contain only Codex-specific notes.
Build & Test Commands
make build # Build binary to ./bin/jk (injects version via ldflags)
make test # Run unit tests (228+ tests)
make lint # Run golangci-lint
make e2e # Run end-to-end tests (requires Docker)
make fmt # Format code with gofmt
# Run a single test
go test -run TestFunctionName ./path/to/package
# Skip e2e tests during unit testing
JK_E2E_DISABLE=1 make test
# E2E with Colima on macOS (if Docker is unreachable)
colima start --network-address
export DOCKER_HOST="unix://$HOME/.colima/default/docker.sock"
make e2e
Required Checks
- Run
make buildandmake testbefore commit. - Run
make e2ewhen Jenkins-facing behavior changes and Docker is available. - Run
gofmt -won touched Go packages.
Architecture
This is jk, a GitHub CLI–style interface for Jenkins controllers written in Go 1.25+.
Code Layout (mirrors gh CLI)
cmd/jk/ → Entry point only; calls internal/jkcmd.Main()
internal/
jkcmd/ → CLI initialization and factory wiring
jenkins/ → HTTP client (go-resty), CSRF crumb handling, capability detection
config/ → YAML configuration (<UserConfigDir>/jk/config.yaml)
secret/ → OS keyring token storage (fallback: encrypted file)
build/ → Version info (injected via ldflags)
log/ → Structured logging (zerolog)
pkg/
cmd/<command>/ → Cobra command implementations (auth, run, job, artifact, etc.)
cmd/shared/ → Shared helpers (output formatting, client resolution)
cmdutil/ → Factory pattern, error handling, exit codes
iostreams/ → I/O abstraction (TTY detection, color, progress)
test/e2e/ → End-to-end tests using testcontainers-go
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.
- 8d ago First seen · 103 lines · 1,057 tokens per session scan A f260a5a30717
jenkins-cli CLAUDE.md is an instructions file published in the GitHub repository avivsinai/jenkins-cli (86 stars, last pushed today), licensed MIT. It adds 1,057 tokens to every session, about $0.0053 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-30.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.