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 skills/zakelfassi/skills-driven-development/cross-compile-matrixnpx skills add zakelfassi/skills-driven-development --skill cross-compile-matrixgit clone --depth 1 https://github.com/zakelfassi/skills-driven-developmentWrote 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/zakelfassi/skills-driven-development/cross-compile-matrix)<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/cross-compile-matrix"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/cross-compile-matrix.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 | $0.00063 | $0.00938 |
| Opus 5 | $0.00032 | $0.00469 |
| Sonnet 5 | $0.00013 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
cross-compile-matrix 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 5d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Compile Matrix
Add a new target triple to the build matrix so CI produces a binary for the new platform.
Inputs
- Target triple (e.g.,
aarch64-apple-darwin,x86_64-pc-windows-gnu) - Cross-compiler image (Docker image or
nativeif the runner natively supports the target) - Smoke test command (a simple invocation to verify the binary works, e.g.,
shipctl --version)
Steps
-
Verify the triple is valid
rustup target list | grep {triple}For Go: check
go tool dist list | grep {os}/{arch}. -
Add the target to the CI matrix Edit
.github/workflows/release.yml— add the triple to thematrix.targetarray:strategy: matrix: include: - target: {triple} runner: ubuntu-latest # or macos-latest, windows-latest cross: true # false if runner supports the target natively image: ghcr.io/cross-rs/{triple}:latest # omit if cross: false -
Add the Makefile target
build-{safe-triple}: cargo build --release --target {triple} mkdir -p dist cp target/{triple}/release/shipctl dist/shipctl-{triple}{safe-triple}replaces-with_in Make target names. -
Register the rustup target (Rust only)
rustup target add {triple}For CI: add to the
rustup target addstep in the workflow. -
Add a smoke test step in the workflow:
- name: Smoke test ({triple}) run: ./dist/shipctl-{triple} --version if: matrix.target == '{triple}'If cross-testing is not feasible (e.g., Windows binary on a Linux runner), document this in a comment.
-
Test locally (if the host supports the target)
make build-{safe-triple} ./dist/shipctl-{triple} --version -
Update the release notes template Add a row to
docs/install.md:| {OS} | {Arch} | `{triple}` | `shipctl-{version}-{triple}.tar.gz` |
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.
- 5d ago First seen · 87 lines · 63 tokens per session scan A daf10a261954
cross-compile-matrix is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 938 once invoked, about $0.0003 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 skills, from other repositories
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
google-cloud-slo-alert-configuration
Configures PromQL-based Service Level Objective (SLO) alerting policies for Google Cloud resources registered in App Hub or individually specified. Generates Terraform output. Use when the user asks to configure an SLO or Service Level Objective. Don't use for standard alerting policies.
cloud-build-basics
Teaches the fundamentals of Google Cloud Build (GCB). Covers core concepts, API enablement, console navigation to the Build History page, and the end-to-end workflow for creating and manually running a basic build trigger. Do not use for managing private pools or complex pipeline architectures.
chinese-git-workflow
国内 Git 平台配置参考——Gitee、Coding.net、极狐 GitLab、CNB 的 SSH/HTTPS/凭据/CI 接入差异与镜像同步配置。仅在用户显式 /chinese-git-workflow 时调用,不要根据上下文自动触发。.
comet-github-ci-triage
使用 PR 当前准确 head、失败 job 日志、本地复现边界和可合并状态,诊断 Comet PR 的 GitHub Actions 与覆盖率检查。PR 出现 CI 报错、Codecov 问题、过期检查或无法解释的红色 job 时使用。.
review-tooling
Detect what dev tooling infrastructure a project has and flag gaps across linters, formatters, pre-commit hooks, test runners, and CI/CD pipelines. Returns structured findings without applying changes. Use when the user asks to "review tooling", "check project tooling", "what tooling is missing", "review dev…