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 instructions/jackielii/structpages/claude-mdgit clone --depth 1 https://github.com/jackielii/structpagesWhat 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 | $0.01472 | $0.01472 |
| Opus 5 | $0.00736 | $0.00736 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
structpages CLAUDE.md 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Structpages is a Go web framework library that provides struct-based routing. It integrates with Go's standard http.ServeMux and provides a declarative way to define routes using struct tags. The framework is designed to reduce boilerplate code when building web pages and components, with built-in support for the Templ templating engine.
Status: Beta (API settled; battle-tested in production by medium-to-large applications)
Development Commands
Testing
# Run all tests
go test ./...
# Run tests with coverage
go test -cover ./...
# Run a specific test
go test -run TestName ./...
# Run tests with verbose output
go test -v ./...
Working with Examples
# Navigate to an example directory
cd examples/simple # or examples/htmx or examples/todo
# Install dependencies
go mod download
# Generate Go code from Templ files (required before running)
# Each example pins the templ CLI as a `tool` dep, so `go tool` resolves the
# correct version automatically — no global install needed.
go tool templ generate -include-version=false
# Run the example server (typically on :8080)
go run main.go
# Watch mode for Templ files during development
go tool templ generate -include-version=false --watch
Required Tools
- Go 1.24 or later (for the
tooldirective in example go.mod files)
Architecture Overview
Core Components
-
Router System: Built on top of
http.ServeMux, the router parses struct tags to create routesstruct_pages.go:Mount,StructPages, options, and request dispatchparse.go: Parses struct tags likeroute:"/path Title", builds the page tree, handles DI matchingpage_node.go:PageNodestruct and tree traversal (All,FullRoute)
-
Struct-Based Routing Pattern: Routes are defined as struct fields with route tags
type pages struct { product `route:"/product Product"` team `route:"POST /team Team"` }Each leaf page handles requests via one of: a
Page()templ method (most common), aPropsmethod (Props-only pages), or aServeHTTPmethod (form actions, redirects). Promoted (embedded) methods are skipped.
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.
- 2d ago First seen · 120 lines · 1,472 tokens per session scan A f7bd2a0bccd4
structpages CLAUDE.md is an instructions file published in the GitHub repository jackielii/structpages (24 stars, last pushed 1mo ago), licensed BSD-3-Clause. It adds 1,472 tokens to every session, about $0.0074 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 instructions, from other repositories
go-micro CLAUDE.md
Instructions for micro/go-micro, covering claude.md - go micro project guide, project overview, build & test, run all tests and run tests for a specific package.
go-micro AGENTS.md
Instructions for micro/go-micro, covering repository agent instructions and pull requests from codex tasks.
jwx AGENTS.md
AGENTS.md instructions for lestrrat-go/jwx, covering agents.md, for module consumers, go version, goexperiment and module path vs physical layout.
azure-sdk-for-go go-examples.instructions.md
Instructions for Azure/azure-sdk-for-go, a project described as: This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at.
azure-sdk-for-go copilot-instructions.md
Copilot instructions for Azure/azure-sdk-for-go, covering generated code — do not suggest changes, prerequisites, local sdk generation and package lifecycle (typespec), authoritative reference and default behaviors.
azure-sdk-for-go go-code.instructions.md
Instructions for Azure/azure-sdk-for-go: All code should follow the guidelines from the Azure Go SDK Guidelines. This document is a summary of the most important guidelines to follow when contributing to the Azure Go SDK.