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/thapaliyabikendra/ai-artifactsWrote 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/commands/thapaliyabikendra/ai-artifacts/impact-analysis)<a href="https://agentmods.dev/commands/thapaliyabikendra/ai-artifacts/impact-analysis"><img src="https://agentmods.dev/badge/commands/thapaliyabikendra/ai-artifacts/impact-analysis.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.00014 | $0.01405 |
| Opus 5 | $0.00007 | $0.00702 |
| Sonnet 5 | $0.00003 | $0.00281 |
| Haiku 4.5 | $0.00001 | $0.00140 |
Grade A, and why
impact-analysis 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 7d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Impact Analysis
Change: $ARGUMENTS.change Scope: $ARGUMENTS.scope
Instructions
Step 1: Understand the Change
- If path provided, read the requirements/feature file
- Extract:
- New entities being added
- Existing entities being modified
- New permissions required
- Business rules affected
- API changes
Step 2: Analyze Domain Impact
Search and analyze:
docs/domain/entities/*.md - Entity definitions
docs/domain/permissions.md - Permission structure
docs/domain/business-rules.md - Business rules
api/src/**/Entities/*.cs - Entity implementations
api/src/**/Permissions/*.cs - Permission definitions
Step 3: Generate Impact Report
# Impact Analysis: [Change Title]
**Date**: [YYYY-MM-DD]
**Analyst**: Claude
**Status**: Draft | Reviewed | Approved
## Executive Summary
[2-3 sentence summary of the change and its overall impact]
**Impact Level**: 🟢 Low | 🟡 Medium | 🔴 High
## Change Overview
### What's Changing
- [Bullet point summary of changes]
### Why It's Changing
- [Business drivers]
## Entity Impact
### New Entities
| Entity | Base Class | Relationships | Notes |
|--------|------------|---------------|-------|
| [Name] | FullAuditedAggregateRoot | [Relations] | [Notes] |
### Modified Entities
| Entity | Change Type | Fields Affected | Migration Required |
|--------|-------------|-----------------|-------------------|
| [Name] | Add Field | [field1, field2] | Yes |
| [Name] | Modify Field | [field] | Yes |
| [Name] | Add Relation | [FK to Entity] | Yes |
### Unchanged but Affected
| Entity | Impact | Reason |
|--------|--------|--------|
| [Name] | Query changes | New join required |
## Database Impact
### Schema Changes
```sql
-- New tables
CREATE TABLE [TableName] (...)
-- Altered tables
ALTER TABLE [TableName] ADD COLUMN [column] [type];
-- New indexes
CREATE INDEX IX_[name] ON [table]([columns]);
Migration Complexity
- New Tables: [count]
- Altered Tables: [count]
- Data Migration: Required | Not Required
- Estimated Downtime: None | < 5 min | > 5 min
Permission Impact
New Permissions
| Permission | Description | Default Roles |
|---|---|---|
| [Module].[Entity].Create | Create [entity] | Admin, Manager |
| [Module].[Entity].Update | Update [entity] | Admin, Manager |
| [Module].[Entity].Delete | Delete [entity] | Admin |
Modified Permissions
| Permission | Change | Affected Roles |
|---|---|---|
| [Existing] | [What changed] | [Roles] |
API Impact
New Endpoints
| Method | Endpoint | Auth | Description |
|---|---|---|---|
| GET | /api/[entity] | [Permission] | List [entities] |
| POST | /api/[entity] | [Permission] | Create [entity] |
Modified Endpoints
| Endpoint | Change Type | Breaking |
|---|---|---|
| /api/[existing] | New parameter | No |
| /api/[existing] | Response change | Yes |
Breaking Changes
| Change | Impact | Migration Path |
|---|---|---|
| [Description] | [Who's affected] | [How to migrate] |
Code Impact
Files to Create
| File | Type | Location |
|---|---|---|
| [Entity].cs | Entity | Domain/Entities |
| [Entity]Dto.cs | DTO | Contracts/Dtos |
| [Entity]AppService.cs | Service | Application |
| [Entity]Validator.cs | Validator | Application |
Files to Modify
| File | Change | Risk |
|---|---|---|
| [File] | [Description] | Low/Med/High |
Tests Required
| Test Type | Count | Priority |
|---|---|---|
| Unit Tests | [N] | P1 |
| Integration Tests | [N] | P1 |
| E2E Tests | [N] | P2 |
Dependency Analysis
Upstream Dependencies
[Systems/modules this change depends on]
| Dependency | Type | Status |
|---|---|---|
| [Name] | API | Ready |
| [Name] | Database | Needs update |
Downstream Impact
[Systems/modules affected by this change]
| Consumer | Impact | Action Required |
|---|---|---|
| [Name] | [Description] | [Action] |
Risk Assessment
| Risk | Likelihood | Impact | Mitigation |
|---|---|---|---|
| [Risk 1] | Low/Med/High | Low/Med/High | [Strategy] |
| [Risk 2] | Low/Med/High | Low/Med/High | [Strategy] |
Implementation Checklist
Phase 1: Preparation
- Database migration script created
- Entity definitions reviewed
- Permission structure approved
Phase 2: Implementation
- Entities created
- DTOs and validators implemented
- AppServices implemented
- Permissions configured
Phase 3: Testing
- Unit tests written
- Integration tests written
- Manual testing completed
Phase 4: Deployment
- Migration tested in staging
- Rollback plan documented
- Monitoring configured
Recommendations
- [Recommendation 1]: [Details]
- [Recommendation 2]: [Details]
- [Recommendation 3]: [Details]
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.
- 7d ago First seen · 236 lines · 14 tokens per session scan A 219c51532880
impact-analysis is a command published in the GitHub repository thapaliyabikendra/ai-artifacts (24 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,405 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.