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 rules/technickai/ai-coding-config/fixing-github-actions-buildsgit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWhat 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.00007 | $0.00574 |
| Opus 5 | $0.00003 | $0.00287 |
| Sonnet 5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
fixing-github-actions-builds 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.
This is a copy
92% identical to fixing-github-actions-builds — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixing Broken GitHub Actions Builds
Purpose
This guide documents the process for diagnosing and fixing broken GitHub Actions builds
using the gh CLI.
Prerequisites
Check if gh is installed
First, verify the GitHub CLI is installed:
gh --version
If gh is not installed
Politely stop and guide the developer:
The GitHub CLI (
gh) is not installed. Let's get that set up first!Installation (macOS):
brew install gh gh auth loginFollow the prompts to authenticate with GitHub. Once complete, we can proceed with debugging the build!
Diagnostic Workflow
Step 1: List Recent Workflow Runs
gh run list --limit 5
Identify the failed run (marked with X or failure status). Note the run ID.
Step 2: Get Failed Logs
gh run view <run-id> --log-failed | cat
This shows ONLY the logs from failed steps. Analyze these logs to identify the root cause.
Step 3: Reproduce Locally
Based on the error in the logs, reproduce the failure locally to verify the fix.
Step 4: Make the Fix
Edit the relevant files to fix the issue identified in the logs.
Step 5: Verify Locally
Test the fix thoroughly to ensure it resolves the issue.
Step 6: Report to Developer
DO NOT commit or push changes!
Report to the developer:
Build issue fixed!
Changes made:
path/to/file: Description of changeNext steps:
- Review the changes with
git statusandgit diff- Test locally if desired
- Commit and push when ready
- Monitor the new build with
gh run watch
Integration with Cursor
When a developer says "the build is broken" or "fix the GitHub Actions build":
- Run
gh --versionto verify installation (stop if not installed) - Run
gh run list --limit 5to see recent runs - Identify the failed run ID
- Run
gh run view <run-id> --log-failed | catto get error details - Analyze the logs and identify root cause
- Fix the issue locally
- Verify the fix works
- Report back to developer with changes and next steps
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 · 104 lines · 7 tokens per session scan A 1dfce5238332
fixing-github-actions-builds is a cursor rule published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 574 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to fixing-github-actions-builds, differing in 1 line, and is treated as a copy.
Other cursor rules, from other repositories
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.