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/jaseci-labs/jac/copilot-instructionsgit clone --depth 1 https://github.com/jaseci-labs/jacWrote 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/jaseci-labs/jac/copilot-instructions)<a href="https://agentmods.dev/instructions/jaseci-labs/jac/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/jaseci-labs/jac/copilot-instructions.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 | $0.00635 | $0.00635 |
| Opus 5 | $0.00318 | $0.00318 |
| Sonnet 5 | $0.00127 | $0.00127 |
| Haiku 4.5 | $0.00064 | $0.00064 |
Grade A, and why
jac 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 5d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Copilot Instructions
Repository Structure
This monorepo contains:
jac/: Jac language compiler, runtime, language server, and the client/desktop runtimes (jac/jaclang/client/)jac-byllm/: LLM integration and model-driven featuresdocs/: Documentation site and reference materialsscripts/: Build, test, and maintenance scripts
Common Workflows
jaclang ships as the single jac binary (a Jac launcher + bundled CPython) -- there is no pip-installed jaclang. Build it and put it on PATH with ./scripts/fresh_env.sh (see CONTRIBUTING.md).
Run tests through the binary's bundled runner (JAC_TEST_JOBS=auto runs them in parallel):
cd jac && JAC_TEST_JOBS=auto jac test tests
Run the formatting/lint gate (same checks the git hook runs):
jac precommit
Package-Specific Notes
jac/ (Compiler & Runtime)
- Grammar:
jac/jaclang/compiler/jac.lark - IR:
unitree.py(UniTree nodes) - Passes:
jac/jaclang/compiler/passes/ - Codegen:
jcir_gen_pass.jac,jcir_bc_gen_pass.jac - Compiler passes subclass
Transform/UniPasswithenter_*/exit_*hooks - Test fixtures:
jac/jaclang/compiler/**/tests/fixtures/ - For type system work, see
.github/agents/type-system-agent.md
jac-byllm/ (LLM Features)
- Core logic:
byllm/lib.py,llm_connector.py - Schema definitions:
schema.py - Examples:
examples/agentic_ai/
Client & Desktop Runtimes
- Now part of
jaclangcore:jac/jaclang/client/
Jac Language Conventions
Import syntax:
import from module { symbol, another_symbol }
import module as alias;
Entry point:
with entry { /* ... */ }
PR Guidelines
- Target repository: Always create PRs against
https://github.com/jaseci-labs/jaseci(not forks). Usegh pr create --repo jaseci-labs/jaseci. - Release notes: If your PR affects Jac developer experience, add a release-note fragment at
release_notes/unreleased/<package>/<PR#>.<category>.md. - Grouping: Organize related changes under sections like "Type Checking Enhancements" or "Cloud Platform Updates".
- Testing: Ensure relevant tests pass before submitting.
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.
- 5d ago First seen · 78 lines · 635 tokens per session scan A 28b3757d98aa
jac copilot-instructions.md is an instructions file published in the GitHub repository jaseci-labs/jac (697 stars, last pushed today), licensed MIT. It adds 635 tokens to every session, about $0.0032 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
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).
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.
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.