Borrowing it
Nothing to install: this file belongs to sjhorn/single_child_two_dimensional_scroll_view. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sjhorn/single_child_two_dimensional_scroll_view/main/.claude/agents/infrastructure.mdgit clone --depth 1 https://github.com/sjhorn/single_child_two_dimensional_scroll_viewWrote 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/sjhorn/single_child_two_dimensional_scroll_view/infrastructure)<a href="https://agentmods.dev/agents/sjhorn/single_child_two_dimensional_scroll_view/infrastructure"><img src="https://agentmods.dev/badge/agents/sjhorn/single_child_two_dimensional_scroll_view/infrastructure/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/sjhorn/single_child_two_dimensional_scroll_view/infrastructure"><img src="https://agentmods.dev/badge/agents/sjhorn/single_child_two_dimensional_scroll_view/infrastructure.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.00025 | $0.00181 |
| Opus 5.5 | $0.00010 | $0.00072 |
| Sonnet 5.5 | $0.00005 | $0.00036 |
| Haiku 4.5 | $0.00003 | $0.00018 |
Grade A, and why
infrastructure 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.
What it actually says
You are the infrastructure agent. You own lib/src/infrastructure/ and test/src/infrastructure/. Never touch the presentation layer.
Allowed imports
import 'dart:async';
import 'package:flutter/foundation.dart';
import 'package:flutter/services.dart';
import '../domain/...';
May import Flutter services and the domain layer. Never import presentation layer.
Workflow
- Write failing test → implement → green →
scripts/ci/ci_gate.sh test/src/infrastructure/ - Commit:
feat(infra):,fix(infra):, ortest(infra):
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 First seen · 25 lines · 25 tokens per session scan A a7df7c625160
infrastructure is an agent published in the GitHub repository sjhorn/single_child_two_dimensional_scroll_view (5 stars, last pushed 7mo ago), licensed BSD-3-Clause. It adds 25 tokens to every session and 181 once invoked, about $0.0001 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-04.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
nestjs-unit-testing-expert
Expert in unit testing with NestJS, Jest, and testing utilities that provides comprehensive test strategies, test architecture, and testing best practices for TypeScript applications. Use PROACTIVELY for writing unit tests, improving test coverage, or reviewing testing strategies in NestJS applications.
implement-agent
Orchestrates full feature implementation across models, controllers, views, and tests following 37signals conventions. WHEN: Implementing a full feature end-to-end, coordinating multi-layer changes, building new CRUD resources. WHEN NOT: Reviewing existing code (use review-agent), refactoring legacy patterns (use…
test-fixtures-preparer
Ensures /conftest.py defines messaging handler fixtures and the makeeventenvelope helper for message-handler tests. Invoke with: @test-fixtures-preparer.
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.