anthropic-policy-guardrails
Implement Anthropic lint rules, policy enforcement, and automated guardrails. Use when setting up code quality rules for Anthropic integrations, implementing pre-commit hooks, or configuring CI policy checks for Anthropic best practices. Trigger with phrases like "anthropic policy", "anthropic lint", "anthropic guardrails", "anthropic best practices check", "anthropic eslint".
Allowed Tools
Provided by Plugin
anthropic-pack
Claude Code skill pack for Anthropic (30 skills)
Installation
This skill is included in the anthropic-pack plugin:
/plugin install anthropic-pack@claude-code-plugins-plus
Click to copy
Instructions
Anthropic Policy & Guardrails
Overview
Automated policy enforcement and guardrails for Anthropic integrations.
Prerequisites
- ESLint configured in project
- Pre-commit hooks infrastructure
- CI/CD pipeline with policy checks
- TypeScript for type enforcement
ESLint Rules
Custom Anthropic Plugin
// eslint-plugin-anthropic/rules/no-hardcoded-keys.js
module.exports = {
meta: {
type: 'problem',
docs: {
description: 'Disallow hardcoded Anthropic API keys',
},
fixable: 'code',
},
create(context) {
return {
Literal(node) {
if (typeof node.value === 'string') {
if (node.value.match(/^sk_(live|test)_[a-zA-Z0-9]{24,}/)) {
context.report({
node,
message: 'Hardcoded Anthropic API key detected',
});
}
}
},
};
},
};
ESLint Configuration
// .eslintrc.js
module.exports = {
plugins: ['anthropic'],
rules: {
'anthropic/no-hardcoded-keys': 'error',
'anthropic/require-error-handling': 'warn',
'anthropic/use-typed-client': 'warn',
},
};
Pre-Commit Hooks
# .pre-commit-config.yaml
repos:
- repo: local
hooks:
- id: anthropic-secrets-check
name: Check for Anthropic secrets
entry: bash -c 'git diff --cached --name-only | xargs grep -l "sk_live_" && exit 1 || exit 0'
language: system
pass_filenames: false
- id: anthropic-config-validate
name: Validate Anthropic configuration
entry: node scripts/validate-anthropic-config.js
language: node
files: '\.anthropic\.json$'
TypeScript Strict Patterns
// Enforce typed configuration
interface AnthropicStrictConfig {
apiKey: string; // Required
environment: 'development' | 'staging' | 'production'; // Enum
timeout: number; // Required number, not optional
retries: number;
}
// Disallow any in Anthropic code
// @ts-expect-error - Using any is forbidden
const client = new Client({ apiKey: any });
// Prefer this
const client = new AnthropicClient(config satisfies AnthropicStrictConfig);
Architecture Decision Records
ADR Template
# ADR-001: Anthropic Client Initialization
## Status
Accepted
## Context
We need to decide how to initialize the Anthropic client across our application.
## Decision
We will use the singleton pattern with lazy initialization.
## Consequences
- Pro: Single client instance, connection reuse
- Pro: Easy to mock in tests
- Con: Global state requires careful lifecycle management
## Enforcement
- ESLint rule: anthropic/use-singleton-client
- CI check: grep for "new AnthropicClient(" outside allowed files
Policy-as-Code (OPA)
# anthropic-policy.rego
package anthropic
# Deny production API keys in non-production environments
deny[msg] {
input.environment != "production"
startswith(input.apiKey, "sk_live_")
msg := "Production API keys not allowed in non-production environment"
}
# Require minimum timeout
deny[msg] {
input.timeout < 10000
msg := sprintf("Timeout too low: %d < 10000ms minimum", [input.timeout])
}
# Require retry configuration
deny[msg] {
not input.retries
msg := "Retry configuration is required"
}
CI Policy Checks
# .github/workflows/anthropic-policy.yml
name: Anthropic Policy Check
on: [push, pull_request]
jobs:
policy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- name: Check for hardcoded secrets
run: |
if grep -rE "sk_(live|test)_[a-zA-Z0-9]{24,}" --include="*.ts" --include="*.js" .; then
echo "ERROR: Hardcoded Anthropic keys found"
exit 1
fi
- name: Validate configuration schema
run: |
npx ajv validate -s anthropic-config.schema.json -d config/anthropic/*.json
- name: Run ESLint Anthropic rules
run: npx eslint --plugin anthropic --rule 'anthropic/no-hardcoded-keys: error' src/
Runtime Guardrails
// Prevent dangerous operations in production
const BLOCKED_IN_PROD = ['deleteAll', 'resetData', 'migrateDown'];
function guardAnthropicOperation(operation: string): void {
const isProd = process.env.NODE_ENV === 'production';
if (isProd && BLOCKED_IN_PROD.includes(operation)) {
throw new Error(`Operation '${operation}' blocked in production`);
}
}
// Rate limit protection
function guardRateLimits(requestsInWindow: number): void {
const limit = parseInt(process.env.ANTHROPIC_RATE_LIMIT || '100');
if (requestsInWindow > limit * 0.9) {
console.warn('Approaching Anthropic rate limit');
}
if (requestsInWindow >= limit) {
throw new Error('Anthropic rate limit exceeded - request blocked');
}
}
Instructions
Step 1: Create ESLint Rules
Implement custom lint rules for Anthropic patterns.
Step 2: Configure Pre-Commit Hooks
Set up hooks to catch issues before commit.
Step 3: Add CI Policy Checks
Implement policy-as-code in CI pipeline.
Step 4: Enable Runtime Guardrails
Add production safeguards for dangerous operations.
Output
- ESLint plugin with Anthropic rules
- Pre-commit hooks blocking secrets
- CI policy checks passing
- Runtime guardrails active
Error Handling
| Issue | Cause | Solution |
|---|---|---|
| ESLint rule not firing | Wrong config | Check plugin registration |
| Pre-commit skipped | --no-verify | Enforce in CI |
| Policy false positive | Regex too broad | Narrow pattern match |
| Guardrail triggered | Actual issue | Fix or whitelist |
Examples
Quick ESLint Check
npx eslint --plugin anthropic --rule 'anthropic/no-hardcoded-keys: error' src/
Resources
Next Steps
For architecture blueprints, see anthropic-architecture-variants.