A command for adding or updating GitHub Actions checks for FHIR resources. GitHub Actions is GitHub's service for running automated tasks when code changes.

Use it to detect resource directories, create a validation workflow, install the needed CLI when necessary, and produce test results for CI.

It removes the manual work of setting up repeatable validation whenever a repository changes, while fitting into existing project scripts where possible.

init-ci — Command for Claude Code by sigistry/marketplace

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add sigistry/marketplace

Claude Code

/plugin install records

Made for: Claude Code.

Or install records, the plugin that ships this one along with the rest of its 3 skills, 5 commands, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sigistry/marketplace/init-ci/github.svg)](https://agentmods.dev/commands/sigistry/marketplace/init-ci)

Your own site

<a href="https://agentmods.dev/commands/sigistry/marketplace/init-ci"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/init-ci/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sigistry/marketplace/init-ci"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/init-ci.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 306 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00011	$0.00306
Opus 5.5	$0.00004	$0.00122
Sonnet 5.5	$0.00002	$0.00061
Haiku 4.5	$0.00001	$0.00031

Measured 1mo ago against content hash b44a706e1e9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

init-ci 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 1mo 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.

plugins/records/commands/init-ci.md · 28 lines

What it actually says

Initialize Records FHIR Validation CI

Use the fhir-ci-quality skill and read skills/fhir-validation/references/quality-rules.md plus skills/fhir-validation/references/ci-templates.md when needed.

Target resource directory: $ARGUMENTS or infer from detector output.

Use this helper for a first draft when the target repository does not already have a better workflow pattern:

node "${CLAUDE_PLUGIN_ROOT}/skills/fhir-validation/scripts/generate-ci.mjs" --dir "$ARGUMENTS"

Steps:

Run the detector script to find source directories, generated directories, package scripts, and existing .github/workflows.
Prefer an existing repository package manager and validation script if present.
Add a GitHub Actions workflow only when the repository has no suitable validation workflow.
Use records validate-file <resource-directory> --format junit for local CLI validation.
Use records --api-url "$RECORDS_API_URL" --auth-token "$RECORDS_API_KEY" ... only when the user asks for API-backed validation.
Add an explicit CLI install step if the repository does not already install Records.

Do not add Firely, HAPI, Java validator, SUSHI, or external terminology services unless the user asks for that validator and consents to the installation/network boundary.

Changes

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.

1mo ago First seen · 28 lines · 11 tokens per session scan A b44a706e1e9d

Subscribe to this mod's changes

init-ci is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 8d ago), licensed MIT. It adds 11 tokens to every session and 306 once invoked, about $0.0000 per session on Opus 5.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-03.

CI and CD Claude Code DevOps and cloud Testing agent-skills claude claude-code-marketplace claude-code-plugin marketplace

test-setup

Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.

furkantokkan/agent-foundry · 45 tokens

validate

Mechanically validate the sonu plugin repo before a PR — manifest sync, YAML frontmatter, shell-fence syntax, named-source and AI-attribution scans, cross-reference integrity, skill reachability. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.

PrabhdeepSingh/claude-plugins · 60 tokens

matrix-cell-onboard

Author and review published PHP/Laravel libraries, map testsuites, and plan version-matrix cells. Routes provider/facade design, Testbench setup, Composer contracts, polyfill audits, suite selection, and cell onboarding to separate modes. Not for application code or single-version framework advice. Output follows the…

hmj1026/dhpk · 65 tokens

init-ci