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/evotecit/chartforgex/agents-mdgit clone --depth 1 https://github.com/EvotecIT/ChartForgeXWhat 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.00482 | $0.00482 |
| Opus 5 | $0.00241 | $0.00241 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
ChartForgeX AGENTS.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 yesterday.
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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidance
ChartForgeX is a dependency-free rendering engine. Keep changes generic, testable, and reusable across SVG, HTML, PNG, reports, dashboards, email, documentation, and static site output.
Boundaries
- Keep
ChartForgeXfree of runtime package dependencies. - Keep static rendering deterministic and script-free by default.
- Put host-specific browser behavior in adapter packages such as
ChartForgeX.Interactivity.Html. - Do not move dashboard shells, filters, inspectors, data collection, Active Directory calculations, or product-specific page layout into ChartForgeX.
- Keep topology product-neutral. Host projects map their own data into
TopologyChart. - Keep non-chart exact facts in
ChartForgeX.VisualBlocks; do not force tables, lists, or KPI cards into chart series.
Change Expectations
- Add or update smoke tests for new renderer behavior.
- Add or update generated examples when a change affects visible output.
- Preserve SVG and PNG parity for visual polish.
- Preserve
net472,netstandard2.0,net8.0, andnet10.0support. - Breaking changes are allowed when they produce a cleaner architecture, better usability, or a simpler public API. Prefer intentional migration notes over compatibility layers that preserve awkward designs.
- Do not add
NoWarnsuppressions. - Keep production source files under the repository line-budget expectation.
- Prefer shared helpers for color math, mark surfaces, line layers, text fitting, map surfaces, and validation instead of local renderer copies.
Documentation
- Keep
README.mdreadable as the product and developer entry point. - Keep durable reference material in focused files under
docs/. - Keep active future work in
TODO.md. - Do not create extra roadmap, handoff, or "next work" documents for ordinary follow-up items.
- Remove stale "next" language once the described work has landed.
Validation
Use the repository quality loop before trusting visual or packaging changes:
./Build.ps1 -Configuration Release
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.
- yesterday First seen · 52 lines · 482 tokens per session scan A 0e6cc286615a
ChartForgeX AGENTS.md is an instructions file published in the GitHub repository EvotecIT/ChartForgeX (45 stars, last pushed 3d ago), licensed MIT. It adds 482 tokens to every session, about $0.0024 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
maui uitests.instructions.md
Instructions for dotnet/maui, covering ui testing guidelines for .net maui, ui test structure, two-project requirement, base class and infrastructure and naming conventions.
maui ci-copilot-pipeline-security.instructions.md
Security rules for the Copilot PR-review pipeline. Read before editing.
maui performance-hotpaths.instructions.md
Instructions for dotnet/maui, covering performance-critical path rules, hot paths in maui, allocation avoidance, caching and invalidation and collection iteration.
maui collectionview-windows.instructions.md
Instructions for dotnet/maui, covering collectionview — windows (items/ handler), winui listview/itemsrepeater patterns, data source and change notifications, layout configuration and cross-platform consistency.
joint CLAUDE.md
Instructions for clientIO/joint, covering claude.md, project overview, common commands, install dependencies and build distribution files (runs grunt).
codex-provider-sync AGENTS.md
Instructions for Dailin521/codex-provider-sync, covering ai / agent operator guide, vnext architecture baseline, goal, choose the interface and safe operating flow.