Borrowing it
Nothing to install: this file belongs to dedsecorg/agentic-dns. 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/dedsecorg/agentic-dns/main/.agents/skills/chunk-sidecar/SKILL.mdgit clone --depth 1 https://github.com/dedsecorg/agentic-dnsWrote 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/dedsecorg/agentic-dns/chunk-sidecar)<a href="https://agentmods.dev/skills/dedsecorg/agentic-dns/chunk-sidecar"><img src="https://agentmods.dev/badge/skills/dedsecorg/agentic-dns/chunk-sidecar/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/dedsecorg/agentic-dns/chunk-sidecar"><img src="https://agentmods.dev/badge/skills/dedsecorg/agentic-dns/chunk-sidecar.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, 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 Privilege Escalation · line 125 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 58 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 220 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 221 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00150 | $0.02888 |
| Opus 5 | $0.00075 | $0.01444 |
| Sonnet 5 | $0.00030 | $0.00578 |
| Haiku 4.5 | $0.00015 | $0.00289 |
Grade A, and why
chunk-sidecar 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 4d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chunk Sidecar
Run your build, test, and validate commands on a remote CircleCI-provisioned Linux environment instead of locally. The 90% job is the sync → validate dev loop. This skill also handles first-time setup, debugging, test-suite scaffolding, and snapshot management.
Step 0 — Probe State, Then Ask
Run these probes before anything else. They are read-only and always safe:
chunk --version 2>&1 || echo "CHUNK_NOT_INSTALLED"
chunk auth status 2>&1
cat .chunk/config.json 2>&1 || echo "{}"
chunk sidecar current 2>&1
If chunk is not installed: Stop. Tell the user to install chunk before using this skill.
If auth shows CircleCI "Not set": Run the OAuth login for them — see Logging in — then re-run chunk auth status. Only continue once CircleCI shows "Configured".
Otherwise, call AskUserQuestion based on detected state (choose the block that matches):
No active sidecar + no validation.sidecarImage in config (first time)
AskUserQuestion:
header: "Sidecar intent"
question: "No sidecar is configured yet. What would you like to do?"
options:
- "Walk me through first-time setup"
→ invoke the chunk-sidecar-setup skill via the Skill tool
- "I have a snapshot ID — create from it"
→ ask user for the snapshot ID, then:
chunk sidecar create --image <id>
chunk sidecar sync
→ continue to Dev Loop section
- "Diagnose what's missing"
→ go to Prerequisites section, report findings
- "Scaffold test-suites.yml for Smarter Testing"
→ go to Scaffolding section
No active sidecar + validation.sidecarImage IS set
AskUserQuestion:
header: "Sidecar action"
question: "You have a configured snapshot but no running sidecar. What would you like to do?"
options:
- "Launch from snapshot and start dev loop" ← Recommended
→ chunk sidecar create --image <sidecarImage>
chunk sidecar sync
→ continue to Dev Loop section
- "Debug or fix something"
→ go to Troubleshooting section
- "Scaffold test-suites.yml"
→ go to Scaffolding section
- "Manage snapshots"
→ go to Snapshot Management section
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.
- 4d ago First seen · 259 lines · 150 tokens per session scan A c083fe4b8145
chunk-sidecar is a skill published in the GitHub repository dedsecorg/agentic-dns (8 stars, last pushed today), licensed MIT. It adds 150 tokens to every session and 2,888 once invoked, about $0.0007 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-09-06.
Other skills, from other repositories
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
ops-nuke-cicd
Designs and troubleshoots NUKE-based CI/CD pipelines for .NET services. Use when refactoring target graphs, splitting test flows, publishing reports, or diagnosing slow pipelines.
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
code-qualities-assessment
Assess code maintainability through 5 foundational qualities (cohesion, coupling, encapsulation, testability, non-redundancy) with quantifiable scoring rubrics. Works at method/class/module levels across multiple languages. Produces markdown reports with remediation guidance. Use when you ask to "assess…
ai-agents-portability-campaign
Execute cross-harness hook changes for Claude Code and GitHub Copilot CLI using the settled official contract, versioned probes, generators, and runtime tests. Use for run the portability campaign, port hooks to a new harness, copilot hook timeout regression, or new copilot cli release, recheck the contract. Do NOT…
chaos-experiment
Design and document chaos engineering experiments. Guide steady state baseline, hypothesis formation, failure injection plans, and results analysis. Use when you say "design a chaos experiment", "plan a game day", "failure injection", "test resilience", or "chaos engineering". Do NOT use for security threat analysis…