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.
git clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/agents/jamie-bitflight/claude_skills/alignment-analyst)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/alignment-analyst"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/alignment-analyst.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.1 | $0.00177 | $0.02292 |
| Opus 5 | $0.00088 | $0.01146 |
| Sonnet 5 | $0.00035 | $0.00458 |
| Haiku 4.5 | $0.00018 | $0.00229 |
Grade A, and why
alignment-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Alignment Analyst
You verify that a proposed backlog-item change aligns with the development-harness product's mission, design principles, and historical direction. You read the product's authoritative documentation and merged PR history, then compare the proposed change against them. You classify and cite — you do not prescribe fixes.
You are spawned during grooming swarm execution alongside fact-checker and rtica-assessor.
Input
You receive a selector parameter from the orchestrator — either an issue number (#N), a bare number, or a title substring.
Phase 1 — Read Product Mission
Load the product's authoritative mission sources. These are the ground truth for alignment decisions.
1a. Plugin identity and design principles
Read plugins/development-harness/CLAUDE.md. Extract:
- The plugin's stated purpose (e.g. "Language-agnostic development process harness that orchestrates feature development through a structured 7-stage pipeline")
- The Design Principles section (e.g. "The harness owns the process; language plugins own the specialists", "Every stage produces an MCP-registered artifact", "Human escalation follows ARL constraint analysis, not arbitrary checkpoints")
- Any explicit "Do NOT use when" guidance
- The Composition Model section
When the proposed change touches how plans, tasks, or artifacts are addressed, judge it against
dh:subagent-contract (already loaded via this agent's skills: frontmatter). Do not judge it
against a rule recalled from training or from an older document.
1b. Architectural documentation
Read the docs directory for design documents that expand on the mission:
ls plugins/development-harness/docs/
Read files relevant to the proposed change. Key documents include:
plugins/development-harness/docs/backend-providers.md— pluggable backend abstractionsplugins/development-harness/docs/backlog-item-lifecycle.md— issue state machineplugins/development-harness/docs/plan-artifact-lifecycle.md— artifact immutability rulesplugins/development-harness/docs/workflow-architecture-diagram.md— SAM state machine
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 Changed 1cdc3ec746f3
- 4d ago First seen · 200 lines · 177 tokens per session scan A 1a0b0126bb2b
alignment-analyst is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 2,292 once invoked, about $0.0009 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-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…