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/sdcorejs/sdcorejs-agent/copilot-instructionsgit clone --depth 1 https://github.com/sdcorejs/sdcorejs-agentWhat 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.01689 | $0.01689 |
| Opus 5 | $0.00844 | $0.00844 |
| Sonnet 5 | $0.00338 | $0.00338 |
| Haiku 4.5 | $0.00169 | $0.00169 |
Grade A, and why
sdcorejs-agent copilot-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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SDCoreJS SDLC Agent - GitHub Copilot Instructions
Use this repo as a Runtime-localized SDLC skill pack for AI-agent, Angular, NestJS, Next.js, product-track, design-track, test-track, and generic harness work.
Dispatch
- Glob
skills/**/*.mdand read frontmatter only. - Match the user request against each skill
description. - Read the selected skill body before acting.
- If no skill matches, invoke
sdcorejs-using-skills.
Resolve track/profile/repository/evidence semantics from the versioned
_refs/shared/system-registry.json. Keep track, stack profile, capability
profile, repository role, artifact owner, and execution host distinct. Current
working directory is not artifact-owner evidence.
If several skills match, apply this priority: explicit skill name, approved-plan execution, product docs/traceability, design handoff, test-only work, dedicated utility intent, confirmed track implementation, then brainstorming for ambiguous scope.
Workflow
Request
-> sdcorejs-brainstorming
-> sdcorejs-spec (approval gate + approved spec snapshot)
-> sdcorejs-plan (approval gate + approved plan snapshot)
-> sdcorejs-execute-plan
ask execution mode only when both modes are feasible
dispatch ai-agent | Core UI angular | nestjs | nextjs | product | design | test | generic harness
-> finish gate and tail chain
tests -> optional sdcorejs-simplify -> affected focused tests
-> review/repair -> documentation/task/memory -> ship gates
Track executors:
- Angular:
sdcorejs-angularonly for Core UI portals/new SDCoreJS portals/approved Core UI migration; plain Angular uses the generic harness - NestJS:
sdcorejs-nestjs - Next.js:
sdcorejs-nextjs - AI-agent:
sdcorejs-ai-agentonly for an approved plan with one engine and one independent capability profile - Product:
sdcorejs-product - Design:
sdcorejs-design - Test:
sdcorejs-test - Generic:
sdcorejs-execute-planharness fallback
Under-specified AI-agent requests return to brainstorming. Test, review, and debug intent keep their dedicated owners. The AI-agent track authors governed application contracts/integration and offline evidence; it does not bundle a provider runtime or imply live verification.
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 · 142 lines · 1,689 tokens per session scan A 49ed4063164b
sdcorejs-agent copilot-instructions.md is an instructions file published in the GitHub repository sdcorejs/sdcorejs-agent (2 stars, last pushed 15d ago), licensed MIT. It adds 1,689 tokens to every session, about $0.0084 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-31.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.