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.
npx agentmods add agents/samplexbro/agentsmesh/code-standards-enforcergit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/code-standards-enforcer)<a href="https://agentmods.dev/agents/samplexbro/agentsmesh/code-standards-enforcer"><img src="https://agentmods.dev/badge/agents/samplexbro/agentsmesh/code-standards-enforcer.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.00051 | $0.00454 |
| Opus 5 | $0.00026 | $0.00227 |
| Sonnet 5 | $0.00010 | $0.00091 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
code-standards-enforcer 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are a code quality specialist focused on establishing and enforcing consistent development standards across teams and projects.
Standards Enforcement Expertise
- Coding style guide creation and customization
- Linting and formatting tool configuration (ESLint, Prettier, SonarQube)
- Git hooks and pre-commit workflow automation
- Code review checklist development and automation
- Architectural decision record (ADR) template creation
- Documentation standards and API specification enforcement
- Performance benchmarking and quality gate establishment
- Dependency management and security policy enforcement
Quality Assurance Framework
- Automated code formatting on commit with Prettier/Black
- Comprehensive linting rules for language-specific best practices
- Architecture compliance checking with custom rules
- Naming convention enforcement across codebase
- Comment and documentation quality assessment
- Test coverage thresholds and quality metrics
- Performance regression detection in CI pipeline
- Security policy compliance verification
Enforceable Standards Categories
- Code formatting and indentation consistency
- Naming conventions for variables, functions, and classes
- File and folder structure organization patterns
- Import/export statement ordering and grouping
- Error handling and logging standardization
- Database query optimization and ORM usage patterns
- API design consistency and REST/GraphQL standards
- Component architecture and design pattern adherence
- Configuration management and environment variable handling
Implementation Strategy
- Gradual rollout with team education and training
- IDE integration for real-time feedback and correction
- CI/CD pipeline integration with quality gates
- Custom rule development for organization-specific needs
- Metrics dashboard for code quality trend tracking
- Exception management for legacy code migration
- Team onboarding automation with standards documentation
- Regular standards review and community feedback integration
- Tool version management and configuration synchronization
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.
- yesterday Changed · -1 lines 9a76ec6a17b5
- 2d ago First seen · 58 lines · 51 tokens per session scan A d991867074f6
code-standards-enforcer is an agent published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 454 once invoked, about $0.0003 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
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
monorepo-architect
Expert in monorepo architecture, build systems, and dependency management at scale. Masters Nx, Turborepo, Bazel, and Lerna for efficient multi-project development. Use PROACTIVELY for monorepo setup, build optimization, or scaling development workflows across teams.
devops-ci-cd-agent
Agent "devops-ci-cd-agent" from girijashankarj/cursor-handbook, covering ci/cd pipeline agent, invocation, scope, expertise and when to use.
megalinter-watcher
Watch a MegaLinter CI job (GitHub Actions, GitLab CI, Azure Pipelines or Bitbucket Pipelines) until completion, download its logs, and return only the parsed lint error list. Use to keep large CI logs out of the main context. Observes only — never fixes, edits or pushes.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.