engineering

engineering is an agent for coding agents from lehre-labs/llmsdottxt-mcp. It costs 0 tokens per session (755 once invoked), scanned A, original, Apache-2.0.

Project-specific engineering rules for llmsdottxt-mcp, covering its architecture, data models, validation, and code organisation.

In plain words
What is it for?
Use them when adding features, checking imports, defining models, validating tool inputs, or extending supported ecosystems and platforms.
Why use it?
They turn broad project principles into concrete checks developers can follow, reducing inconsistent designs and accidental dependency or typing problems.

Agent

Install

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.

agentmods
npx agentmods add agents/lehre-labs/llmsdottxt-mcp/engineering
Clone the repo
git clone --depth 1 https://github.com/lehre-labs/llmsdottxt-mcp

Wrote 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.

agentmods badge for engineering

README.md
[![agentmods](https://agentmods.dev/badge/agents/lehre-labs/llmsdottxt-mcp/engineering.svg)](https://agentmods.dev/agents/lehre-labs/llmsdottxt-mcp/engineering)
Your own site
<a href="https://agentmods.dev/agents/lehre-labs/llmsdottxt-mcp/engineering"><img src="https://agentmods.dev/badge/agents/lehre-labs/llmsdottxt-mcp/engineering.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 755 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00755
Opus 5 $0.00000 $0.00378
Sonnet 5 $0.00000 $0.00151
Haiku 4.5 $0.00000 $0.00076

Measured 3d ago against content hash c583969994ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

engineering 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 3d 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.

docs/agents/engineering.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Engineering Rules

Concrete, checkable constraints for llmsdottxt-mcp. AGENTS.md holds the principles; this is the project-specific detail they operate on.

Layered architecture

Imports flow downward only (enforced by import-linter -- uv run lint-imports):

cli -> server -> tools / resources / prompts -> pipeline
    -> scanners / resolvers / platforms / fetcher / index -> http -> config / errors -> models
  • pipeline is the single orchestrator that wires the discovery layer.
  • resolvers/, platforms/, scanners/ are registry packages -- add an ecosystem or platform by dropping a module in and registering it via the package's registry.py.

Typed boundaries

  • Aliases and finite enums live in models/strings.py: StrEnum for protocol values (Ecosystem, Platform, DocsUrlSource), a Literal for LogLevel.
  • Pydantic over dict[str, Any]. Models split by role: core.py (domain), index.py (persisted), responses.py (tool-facing), strings.py (aliases/enums).
  • Validate tool inputs strictly (PackageName, SearchQuery); keep fetched docs tolerant.
  • Field and tool-return types must be importable at runtime, not under TYPE_CHECKING.
  • External docs (this project's own dogfood): Pydantic https://pydantic.dev/llms.txt, FastMCP https://gofastmcp.com/llms.txt.

MCP contracts

  • Tools stay thin: validate the signature, then delegate to pipeline/index. Return Pydantic models; docstrings drive agent routing.
  • Convert internal errors to fastmcp.exceptions.ToolError at the boundary.
  • Read-only context = llmstxt:// resources; actions = tools.

Observability & safety

  • stdout is the MCP stdio channel -- never print() in library code; logs are JSON on stderr via structlog. Exception: cli.py prints tab-separated rows via plain print() (no Rich tables).
  • Route all HTTP through llmsdottxt_mcp.http (get/stream); one shared AsyncClient per scan. get retries transient errors (incl. 429/503, honoring Retry-After) and raises BlockedByChallengeError on an unsolvable WAF challenge -- the pipeline counts those as blocked, not missing.
  • Fetched llms.txt is untrusted: http(s) only, cap size (settings.max_full_text_size), never execute. Log URLs and sizes, never bodies. The ~/.llms.txt.d/ cache is gitignored -- never commit it.

Read the full file on GitHub · 54 lines

Changes

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.

  1. 3d ago First seen · 54 lines · 0 tokens per session scan A c583969994ec

Subscribe to this mod's changes

engineering is an agent published in the GitHub repository lehre-labs/llmsdottxt-mcp (1 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 755 tokens. 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-31.

Related

Other agents, from other repositories

TEAM_USAGE

Agent "TEAM_USAGE" from Auriti-Labs/geo-optimizer-skill, covering agent team usage guide, geoready / geo optimizer, 1. agent inventory, 2. read-only reviewers and 3. code-writing implementation agents.

Auriti-Labs/geo-optimizer-skill · 0 tokens

geo-qa-verifier

Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.

Auriti-Labs/geo-optimizer-skill · 42 tokens

geo-wordpress-connector-architect

Designs the future lightweight WordPress connector for GeoReady, including API-key connection, site metadata, sitemap/CPT/WooCommerce/ACF detection, admin widget, security, and least-privilege architecture.

Auriti-Labs/geo-optimizer-skill · 51 tokens

geoready-dashboard-ui

Designs and implements GeoReady dashboard UI, React/Astro frontend components, empty/loading/error states, premium gating, accessible UX, and claim-safe product copy.

Auriti-Labs/geo-optimizer-skill · 38 tokens

geoready-platform-api

Designs and implements GeoReady platform backend, API routes, database models, migrations, services, entitlements, scheduler jobs, and integration with GEO Optimizer JSON output.

Auriti-Labs/geo-optimizer-skill · 40 tokens

geo-security-privacy-reviewer

Reviews GeoReady/GEO Optimizer changes for SSRF, unsafe URL handling, log upload privacy, API key leakage, ownership isolation, crawler spoofing caveats, WordPress security, and LLM data handling.

Auriti-Labs/geo-optimizer-skill · 50 tokens