foundry
claudeClaude Code configuration and workflow maintenance: 11 skills, 10 specialist agents, rules, hooks, audit, calibration, and session handover
11 skills · 10 agents · hooks
Open-source maintenance: issue and repository analysis, PR review, feedback resolution, release-readiness assessment, setup, and 4 specialist agents
Plugin oss from marketplace borda-ai-rig in Borda/AI-Rig. Commands read from the repo's manifest — today.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
analyseAnalyze GitHub issues, Pull Requests (PRs), Discussions, and repo vitality for an Open Source Software (OSS) project. For any specific item, casts a wide net — finds and lists all related open and closed issues/PRs/discussions, explicitly flags duplicates. Summarizes long threads, extracts reproduct
releasePrepare release communication and check readiness. Main mode: notes with optional flags --changelog, --summary, --migration, --append (incremental: reruns the full pipeline scoped to newly-landed commits, integrating results into existing DRAFT.md/CHANGELOG.md/SUMMARY.md/MIGRATION.md instead of full
resolveOSS maintainer fast-close workflow for GitHub PRs. Three phases: (1) PR intelligence — reads full thread, linked issues, PR body to synthesize contribution motivation and classify every comment into action items; (2) conflict resolution — checks out PR branch (fork-aware via gh pr checkout), merges
reviewMulti-agent code review of GitHub Pull Requests (Python source, documentation (Markdown/RST), and CI/CD config PRs) covering architecture, tests, performance, docs, lint, security, and API design. TRIGGER when: user provides a GitHub PR number (e.g. 42, #42) and asks to review/audit/check it, or pro
setupPost-install setup for the oss plugin. Run once after installing on a new machine, or after a plugin version upgrade, to deliver this plugin's rules/*.md into ~/.claude/rules/ as namespaced symlinks and merge its own permissions.allow and permissions.deny entries into ~/.claude/settings.json. TRIGGE
cicd-stewardCI/CD health specialist, Python/GitHub Actions only — failing CI runs, build times, test matrices, caching, SHA pinning. NOT for ruff/mypy config (foundry:linting-expert), PyPI release/CHANGELOG (oss:shepherd), non-GitHub-Actions platforms. TRIGGER: failing CI runs, slow builds, caching/SHA-pinning
gh-scraperFetches all GitHub API data for a repo (REST + GraphQL) in two sequential groups with parallel calls inside each; writes raw JSONL for oss:repo-warden axis scorers. TRIGGER when: spawned by /oss:analyse (vitality mode) to fetch raw GitHub data. NOT for axis scoring or report generation. NOT for dire
repo-wardenScores an assigned group of vitality axes from a pre-fetched DATA_FILE using vitality-scoring.md; writes partial scores JSON for /oss:analyse assembly. TRIGGER when: spawned 3× in parallel by /oss:analyse (vitality mode) to score axis groups A, B, or C. NOT for raw data fetching (oss:gh-scraper), NO
shepherdOSS shepherd, Python/ML/CV/AI — contributor communication (reply/PR drafts, triage recommendations), release coordination (SemVer, PyPI, CHANGELOG). NOT for thread triage reports (/oss:analyse), docstrings/README (foundry:doc-scribe), CI/publish YAML (oss:cicd-steward), diff review (/oss:review), CH
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/audit-close.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-review-header.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-analyse-header.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/audit-close.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-review-header.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-analyse-header.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-resolve-table.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/agent-router.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/allow-dispatch.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/write-guard.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/audit-close.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exit 0; done; echo "oss plugin hooks are inactive: Node.js not found on PATH, in /opt/homebrew/bin or in
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/audit-close.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/stale-plugin-check.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-review-header.js"; done; exit 0
for n in node /opt/homebrew/bin/node /usr/local/bin/node; do command -v "$n" >/dev/null 2>&1 && exec "$n" "${CLAUDE_PLUGIN_ROOT}/hooks/enforce-analyse-header.js"; done; exit 0
Claude Code configuration and workflow maintenance: 11 skills, 10 specialist agents, rules, hooks, audit, calibration, and session handover
11 skills · 10 agents · hooks
Fifteen evidence-first Codex workflows, one legacy-shim lifecycle manager, fifteen specialist role cards, shared gates, and reviewable artifacts.
16 skills · hooks
Reviewable ML research: literature, planning, methodology review, bounded runs, sweeps, implementation verification, ablations, retrospectives, Kaggle, and setup
10 skills · 2 agents · hooks
Validate-first Python development: plan, feature, fix, refactor, debug, review, and setup workflows
7 skills · hooks
bridge_CC-Codex: guided setup plus bounded implementation, advice, and review across Claude Code and Codex.
7 skills
Static Python structure for Claude Code: indexing, queries, test impact, reference renames, integration, and session telemetry debriefs
6 skills
Legacy core-only installation. For the release-managed bundle of every skill, install hyperframes@hyperframes and then uninstall core-skills@hyperframes.
22 skills
Headroom startup hooks for Claude Code and GitHub Copilot CLI.
hooks
Research any topic across Reddit, X, YouTube, TikTok, Instagram, Hacker News, Polymarket, GitHub, and 5+ more sources. AI agent scores by upvotes, likes, and real money - not editors.
1 skill
Install the "OSS Maintainer" workflow plugin from Agentic Awesome Skills.
10 skills
Set up endorctl and use Endor Labs to scan, prioritize, and fix security risks across your software supply chain
12 skills · 11 agents · hooks
CI/CD pipeline configuration, GitHub Actions/GitLab CI workflow setup, and automated deployment pipeline orchestration
4 skills · 1 command · 5 agents
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.