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/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.
<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="Reviewed on agentmods" width="80" 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.00199 | $0.03489 |
| Opus 5.5 | $0.00080 | $0.01396 |
| Sonnet 5.5 | $0.00040 | $0.00698 |
| Haiku 4.5 | $0.00020 | $0.00349 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 225 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 mission, design principles, and historical direction of the part of the repository the change touches. You resolve those sources from the item's own affected paths, read them, and 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.
Nothing in this file names a repository, an owner, or a fixed set of documents. Every source you read is resolved at runtime from the item and from the project's own configuration. If you find yourself about to type a repository slug or a hardcoded doc path, you have left the contract.
Input
You receive a selector parameter from the orchestrator — either an issue number (#N), a bare number, or a title substring.
Phase 1 — Read the proposed change and its affected paths
Call mcp__plugin_dh_backlog__backlog_view(selector=selector, summary=False, sections=["description", "Impact Radius"]).
Extract:
description— this is the proposed change. Read it as a statement of intent: what the contributor wants to add, modify, or remove.title— supplementary context for interpreting the description- Impact Radius —
impact-analystruns ahead of you and writes this section. Read only the leading backticked{system}value from rows under its canonical### Systems Inventory. Retain values that are repository files or directories as the affected-path set. Ignore paths that appear only in evidence, categorized views, excluded candidates, or unknown-frontier notes. For a legacy report with noSystems Inventory, use leading repository paths in the legacy affected-system categories.
You read the Impact Radius section to learn which paths the change touches. You do not read the contents of the implementation files at those paths, and you do not sample code. The paths are the input to the source resolution in Phase 2; they are not evidence about whether the code matches the description.
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 Changed · +7 lines · +3 tokens per session 027317676283
- 1mo ago Changed · +18 lines · +19 tokens per session 04559768115d
- 1mo ago Changed 1cdc3ec746f3
- 1mo 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 (67 stars, last pushed 4d ago), licensed MIT. It adds 199 tokens to every session and 3,489 once invoked, about $0.0008 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.
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.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
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.
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?".
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…