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 agentmods add instructions/thiagoguislotti/copilot-instructions/ci-cd-devopsgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWhat 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 | $0.03626 | $0.03626 |
| Opus 5 | $0.01813 | $0.01813 |
| Sonnet 5 | $0.00725 | $0.00725 |
| Haiku 4.5 | $0.00363 | $0.00363 |
Grade A, and why
copilot-instructions ci-cd-devops.instructions.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 2d 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 — 648 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline
- Separate build/test/package/deploy stages
- parallel where possible
- fail-fast
- artifact management
- environment promotion
- rollback
- infrastructure as code
stages:
- build
- test
- package
- deploy
jobs:
build:
steps:
- task: DotNetCoreCLI@2
inputs:
command: 'restore'
projects: '**/*.csproj'
- task: DotNetCoreCLI@2
inputs:
command: 'build'
projects: '**/*.csproj'
test:
dependsOn: build
steps:
- task: DotNetCoreCLI@2
inputs:
command: 'test'
projects: '**/*Tests.csproj'
package:
dependsOn: test
steps:
- task: DotNetCoreCLI@2
inputs:
command: 'publish'
publishWebProjects: true
arguments: '--configuration Release --output $(Build.ArtifactStagingDirectory)'
- task: PublishBuildArtifacts@1
inputs:
PathtoPublish: '$(Build.ArtifactStagingDirectory)'
ArtifactName: 'drop'
publishLocation: 'Container'
deploy:
dependsOn: package
environment: 'production'
strategy:
runOnce:
deploy:
steps:
- task: AzureRmWebAppDeployment@4
inputs:
ConnectionType: 'AzureRM'
azureSubscription: 'subscription'
appType: 'webApp'
WebAppName: 'myapp'
packageForLinux: '$(System.ArtifactsDirectory)/drop/**/*.zip'
CI
- Triggers on PRs
- multi-platform builds
- test pyramid automation
- coverage thresholds
- static analysis
- dependency and secret scanning
trigger:
- main
- feature/*
pr:
- main
pool:
vmImage: 'ubuntu-latest'
strategy:
matrix:
Windows:
vmImage: 'windows-latest'
Linux:
vmImage: 'ubuntu-latest'
steps:
- task: UseDotNet@2
inputs:
version: '8.x'
- task: DotNetCoreCLI@2
inputs:
command: 'restore'
projects: '**/*.csproj'
- task: DotNetCoreCLI@2
inputs:
command: 'build'
projects: '**/*.csproj'
- task: DotNetCoreCLI@2
inputs:
command: 'test'
projects: '**/*Tests.csproj'
arguments: '--configuration Release --collect "Code coverage"'
- task: PublishCodeCoverageResults@1
inputs:
codeCoverageTool: 'Cobertura'
summaryFileLocation: '$(Agent.TempDirectory)/**/coverage.cobertura.xml'
reportDirectory: '$(Agent.TempDirectory)/**/coverage'
failIfCoverageEmpty: true
- task: SonarQubePrepare@4
inputs:
SonarQube: 'SonarQube'
scannerMode: 'MSBuild'
projectKey: 'myproject'
projectName: 'My Project'
- task: SonarQubeAnalyze@4
- task: SonarQubePublish@4
inputs:
pollingTimeoutSec: '300'
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.
- 2d ago First seen · 648 lines · 3,626 tokens per session scan A be87e8220029
copilot-instructions ci-cd-devops.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 3,626 tokens to every session, about $0.0181 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-31.
Other instructions, from other repositories
kubevirt-tekton-tasks AGENTS.md
Instructions for kubevirt/kubevirt-tekton-tasks, covering kubevirt tekton tasks - project guide, jira task management, documentation, project structure and key relationships.
foundry-local cpp-ci-test-policy.instructions.md
Use when adding a new test fixture, modality, or model dependency to the C++ integration test suite, or when debugging unexpected GTESTSKIP messages in CI.
docker-zoneminder CLAUDE.md
Instructions for jantman/docker-zoneminder, covering claude.md, project overview, build and test, ci/cd and architecture.
Powershell-Copilot-Standards cicd.instructions.md
Sets up comprehensive CI/CD pipelines for PowerShell projects with automated testing and deployment.
local-ci CLAUDE.md
Claude Code instructions for redwoodjs/local-ci, covering local ci — agent instructions, rules, ci and code.
pipelines CLAUDE.md
Instructions for rios0rios0/pipelines, covering claude.md, what this is, commands, architecture and 5-stage pipeline model.