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.
git clone --depth 1 https://github.com/srnichols/plan-forgeWrote 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/instructions/srnichols/plan-forge/graphql)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/graphql"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/graphql/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/instructions/srnichols/plan-forge/graphql"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/graphql.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.02243 | $0.02243 |
| Opus 5.5 | $0.00897 | $0.00897 |
| Sonnet 5.5 | $0.00449 | $0.00449 |
| Haiku 4.5 | $0.00224 | $0.00224 |
Grade A, and why
plan-forge graphql.instructions.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 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.
How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
.NET GraphQL Patterns (Hot Chocolate)
Schema Design (Code-First)
Modular Root Types with ExtendObjectType
// ✅ Separate domains into their own query files
[ExtendObjectType(typeof(Query))]
public class ProducerQueries
{
[Authorize]
public async Task<Producer?> GetProducerByIdAsync(
Guid id,
[Service] IProducerRepository repository,
CancellationToken ct)
{
return await repository.GetByIdAsync(id, ct);
}
[UsePaging(IncludeTotalCount = true)]
[UseFiltering]
[UseSorting]
public IQueryable<Producer> GetProducers([Service] IProducerRepository repository)
=> repository.GetQueryable();
}
// ❌ NEVER: One massive Query class with all resolvers
Registration
builder.Services
.AddGraphQLServer()
.AddQueryType<Query>()
.AddTypeExtension<ProducerQueries>()
.AddTypeExtension<UserQueries>()
.AddMutationType<Mutation>()
.AddTypeExtension<ProducerMutations>()
.AddSubscriptionType<Subscription>()
.AddAuthorization()
.AddFiltering()
.AddSorting()
.AddProjections()
.AddInMemorySubscriptions()
.AddMaxExecutionDepthRule(10)
.AddQueryCostOptions(o => { o.MaxFieldCost = 10; o.MaxTypeCost = 1000; });
DataLoaders (N+1 Prevention)
// ✅ Batch load — single query for all requested IDs
public class ProducerByIdDataLoader : BatchDataLoader<Guid, Producer>
{
private readonly IProducerRepository _repository;
public ProducerByIdDataLoader(
IProducerRepository repository,
IBatchScheduler batchScheduler,
DataLoaderOptions? options = null)
: base(batchScheduler, options)
{
_repository = repository;
}
protected override async Task<IReadOnlyDictionary<Guid, Producer>> LoadBatchAsync(
IReadOnlyList<Guid> keys,
CancellationToken ct)
{
// ✅ Single batch query — WHERE id = ANY(@Ids)
var producers = await _repository.GetByIdsAsync(keys, ct);
return producers.ToDictionary(p => p.Id);
}
}
// ✅ Usage in resolver
public async Task<Producer?> GetProducerAsync(
[Parent] Order order,
ProducerByIdDataLoader loader,
CancellationToken ct)
{
return await loader.LoadAsync(order.ProducerId, ct);
}
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 · 334 lines · 2,243 tokens per session scan A 888733eb0786
plan-forge graphql.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed 8d ago), licensed MIT. It adds 2,243 tokens to every session, about $0.0090 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-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.