innovation-lab-examples general.instructions.md

Project instructions for an Internet Computer backend written in TypeScript with the Azle development kit; the backend is a web API tested with Jest.

In plain words
What is it for?
Use it when modifying the backend, formatting TypeScript, regenerating Candid interfaces, or deciding how to test and review a change.
Why use it?
It gives contributors shared rules for formatting code, handling interface changes, getting help from AI, and testing changes.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/fetchai/innovation-lab-examples/general
Clone the repo
git clone --depth 1 https://github.com/fetchai/innovation-lab-examples

Made for: GitHub Copilot.

Per session 184 This file is loaded in full into every session.
When invoked 184 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00184 $0.00184
Opus 5 $0.00092 $0.00092
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00018 $0.00018

Measured 2d ago against content hash 1412675519c2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

innovation-lab-examples general.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.

web3/internet-computer/.github/instructions/general.instructions.md · 32 lines

What it actually says

General Instructions

Project Context

  • This is an Internet Computer Protocol (ICP) project using Typescript for canister development with Azle Development Kit.
  • The backend is tested with Jest.
  • There isn't a frontend, since this is a Web API project.

Code Quality & Formatting

  • We use prettier for formatting and linting TypeScript code.
  • Run npm run format for formatting typescript.

AI Assistance

  • Before implementing new features, consider asking human a few clarification questions.
  • If you would like to go beyond the scope of the prompt, please ask the human for permission first.
  • When finishing a significant change, please PAUSE and ask the human for review and permission to continue.

Development Commands

Backend Changes

# Regenerate candid after interface changes
dfx generate
Changes

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.

  1. 2d ago First seen · 32 lines · 184 tokens per session scan A 1412675519c2

Subscribe to this mod's changes

innovation-lab-examples general.instructions.md is an instructions file published in the GitHub repository fetchai/innovation-lab-examples (1,148 stars, last pushed 19d ago), licensed MIT. It adds 184 tokens to every session, about $0.0009 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.