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 agents/jeftarmascarenhas/context-mesh/agent-cicdgit clone --depth 1 https://github.com/jeftarmascarenhas/context-meshWrote 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/agents/jeftarmascarenhas/context-mesh/agent-cicd)<a href="https://agentmods.dev/agents/jeftarmascarenhas/context-mesh/agent-cicd"><img src="https://agentmods.dev/badge/agents/jeftarmascarenhas/context-mesh/agent-cicd.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.00000 | $0.00758 |
| Opus 5 | $0.00000 | $0.00379 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
agent-cicd 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 6d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: CI/CD - Todo App
Purpose
Create GitHub Actions workflows for continuous integration and deployment.
Context Files to Load
- @context/intent/feature-ci-cd.md
- @context/decisions/006-ci-cd-pipeline.md
- @context/decisions/007-deployment-platforms.md
- @context/knowledge/patterns/github-actions.md
Scope
- Allowed:
.github/workflows/, root config files - Prohibited: Modify application code
Execution Steps
-
Create Backend Workflow
- Create
.github/workflows/backend.yml - Trigger on push/PR to main
- Steps: checkout, setup Node, install, lint, test
- Optional: deploy to Railway on main push
- Create
-
Create Frontend Workflow
- Create
.github/workflows/frontend.yml - Trigger on push/PR to main
- Steps: checkout, setup Node, install, lint, test, build
- Optional: deploy to Vercel on main push
- Create
Expected Output
.github/workflows/backend.yml
name: Backend CI
on:
push:
branches: [main]
paths: ['backend/**']
pull_request:
branches: [main]
paths: ['backend/**']
jobs:
test:
runs-on: ubuntu-latest
defaults:
run:
working-directory: backend
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '18'
cache: 'npm'
cache-dependency-path: backend/package-lock.json
- run: npm ci
- run: npm run lint
- run: npm test -- --coverage
.github/workflows/frontend.yml
name: Frontend CI
on:
push:
branches: [main]
paths: ['frontend/**']
pull_request:
branches: [main]
paths: ['frontend/**']
jobs:
test:
runs-on: ubuntu-latest
defaults:
run:
working-directory: frontend
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '18'
cache: 'npm'
cache-dependency-path: frontend/package-lock.json
- run: npm ci
- run: npm run lint
- run: npm test -- --coverage
- run: npm run build
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.
- 6d ago First seen · 123 lines · 0 tokens per session scan A 0c3e00c97742
agent-cicd is an agent published in the GitHub repository jeftarmascarenhas/context-mesh (39 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 758 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 agents, from other repositories
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
pr-watch
Collect the current CI state of a GitHub PR and the logs of any failing jobs. Mechanical data-gathering only - it classifies and reports, it does not fix anything. Use to snapshot PR status before deciding what to do.
ci
GitHub Actions, CI/CD workflows, and automation pipelines. Delegate when the issue involves .github/workflows/, CI configuration, or automated checks.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
polyglot-architect
Cross-language API design and binding parity.
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.