Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/it235/multica-best-practicesnpx agentmods add skills/it235/multica-best-practices/multica-platform-jenkinsWrote 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/it235/multica-best-practices/multica-platform-jenkins)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-platform-jenkins"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-jenkins/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/it235/multica-best-practices/multica-platform-jenkins"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-platform-jenkins.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 14 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00000 | $0.00873 |
| Opus 5 | $0.00000 | $0.00436 |
| Sonnet 5 | $0.00000 | $0.00175 |
| Haiku 4.5 | $0.00000 | $0.00087 |
Grade A, and why
multica-platform-jenkins 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 11d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform · Jenkins (placeholder shell)
This is a platform-layer placeholder shell. The public multica-best-practices binds to no specific company's internal URLs or credentials. To onboard your own CI/CD system, only edit this skill's
config.yamlandscripts/; all upstream orchestration skills stay untouched.
Purpose
CI/CD system read + write: trigger Jobs, poll builds, fetch consoleText, return build URLs.
Parameter auto-discovery: connect to the CI system API to read each Job's required parameters; Agents must not hardcode parameter names.
Default CI URL configured in config.yaml → cicd.base_url (placeholder: http://<your-cicd-host>).
Agent standard flow (required)
1. Resolve service (jobs-catalog / issue_service_map) + **deploy branch** (from the Issue source + affected ends, not feature; for linked Issues use the branch in the external system)
2. discover (required) — default copy from lastSuccessfulBuild, only override deploy branch
3. ready=false → fill missing params or BLOCKED ask human
4. trigger: multica-artifact-cicd-sync → trigger script
Parameter priority: --param > branch hint (branchName etc.) > last SUCCESS build params > CI default
Files (suggested structure)
multica-platform-jenkins/
├── SKILL.md
├── config.yaml
├── jobs-catalog.yaml # per-env Job list (service → Job name)
├── .env.example
└── scripts/
├── trigger_env.py # trigger by env + service
├── list_jobs.py # list / query Jobs
├── cicd_cli.py # low-level API
└── lib/
Install deps (once)
pip install -r scripts/requirements.txt
List Jobs
python scripts/list_jobs.py --env dev
python scripts/list_jobs.py --env sit --service <service>
Discover parameters (live from CI, per Job)
python scripts/cicd_cli.py discover-params --env sit --service <service> --branch release/<ISSUE>-<slug> --json
Trigger build (auto-params by default)
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.
- 11d ago First seen · 98 lines · 0 tokens per session scan A 8468ef8ec374
multica-platform-jenkins is a skill published in the GitHub repository it235/multica-best-practices (108 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 873 tokens. 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 skills, from other repositories
import-prom-rule
Bulk import of a Prometheus alert rule YAML file (create a whole set of rules at once). Dedicated to handling a remote URL or local YAML text, automatically parsing the three formats groups / a plain rules array / a single rule. ⚠️ Do not use this skill for single-rule creation — when the user describes a single alert…
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…
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.