Borrowing it
Nothing to install: this file belongs to ThiagoGuislotti/copilot-instructions. 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/ThiagoGuislotti/copilot-instructions/main/.github/instructions/nettoolskit-rules.instructions.mdgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/nettoolskit-rules)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/nettoolskit-rules"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/nettoolskit-rules.svg" alt="Measured on agentmods" 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.00800 | $0.00800 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
copilot-instructions nettoolskit-rules.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 6d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NetToolsKit README Overrides
Purpose: apply only the NetToolsKit-specific deltas that override the generic baseline in .github/instructions/readme.instructions.md.
Do not restate generic README rules here.
Language Override
- All READMEs must be written in English.
- Code comments inside examples must be English too.
Root README Override
- Keep only these sections, in this order:
- Introduction
- Features
- Contents
- Build and Tests
- Contributing
- Dependencies
- References
- License
- Do not include code examples in the root README.
- Do not include Installation, Quick Start, Usage Examples, or API Reference in the root README.
- The root
Referencessection must list every package README undersrc/*.
Package README Override (src/*)
- Keep only these sections, in this order:
- Introduction
- Features
- Contents
- Installation
- Quick Start
- Usage Examples
- API Reference
- References
- License
- Remove
Build and Tests,Contributing, andDependenciesfrom package READMEs. Usage Examplesmust be organized into numbered subsections with descriptive titles when the package has more than one meaningful scenario.API Referencemust be grouped by logical areas when the public surface is broad.- When public enums exist, add a subsection per enum with a Markdown table of values and concise descriptions.
- When examples introduce structured payloads, add a compact
Data Shapestable withField,Description, andExample.
Coverage Override
- Each package README must cover at least 70% of the key public APIs or features intended for consumer usage.
- Measure coverage against the items intentionally documented in
API Reference. - Prefer runnable, focused examples over placeholders or speculative snippets.
Formatting Override
- Use
Contentsinstead ofTable of Contents. - When
Usage ExamplesorAPI Referencecontain subsections,Contentsmust include nested links for those subsection headings in the same order. - Features bullets must use
- ✅ .... - Package top-level section headings must use
##. - Insert
---between major sections to preserve house style. - License section format is strict:
- Heading:
## License - Body:
This project is licensed under the MIT License. See the LICENSE file at the repository root for details. - Follow with
---
- Heading:
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.
- 6d ago First seen · 81 lines · 800 tokens per session scan A 59f5e2a0db16
copilot-instructions nettoolskit-rules.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 800 tokens to every session, about $0.0040 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
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.
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.
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).
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.