vytalLink: Instructions file for Codex

AGENTS.md

vytalLink AGENTS.md is an instructions file for Codex, OpenCode from xmartlabs/vytalLink. It costs 849 tokens per session, scanned A, original, MIT.

Repository instructions for vytalLink, a health-data platform with a Flutter mobile app, MCP servers, agent examples, a landing site, and shared documentation. They cover the project layout, build commands, checks, and testing rules.

In plain words
What is it for?
Building and testing the Flutter app, MCP servers, landing site, and agent examples, while following the repository’s formatting and integration-check process.
Why use it?
They give coding agents the commands and structure needed to work safely across the repository’s mobile, server, website, example, and documentation parts.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is xmartlabs/vytalLink's own configuration. It tells Codex and OpenCode how to work on vytalLink itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vytalLink configures →

Reuse

Borrowing it

Nothing to install: this file belongs to xmartlabs/vytalLink. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/xmartlabs/vytalLink/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/xmartlabs/vytalLink

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for vytalLink AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/xmartlabs/vytallink/agents-md.svg)](https://agentmods.dev/instructions/xmartlabs/vytallink/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/xmartlabs/vytallink/agents-md"><img src="https://agentmods.dev/badge/instructions/xmartlabs/vytallink/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 849 This file is loaded in full into every session.
When invoked 849 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00849 $0.00849
Opus 5 $0.00425 $0.00425
Sonnet 5 $0.00170 $0.00170
Haiku 4.5 $0.00085 $0.00085

Measured 6d ago against content hash 157f2d15ba45, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

vytalLink 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 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.

AGENTS.md · 46 lines

How it starts

The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

Project Structure & Module Organization

  • mobile/: Flutter app + MCP server; code in lib/, design system in design_system/, env samples in environments/.
  • landing/: Firebase site with HTML/JS under public/ and CSS partials in public/styles/.
  • mcp-server/: Node MCP server exported as @xmartlabs/vytallink-mcp-server; main file vytalLink_mcp_server.js.
  • examples/: TypeScript and Python CLI agent examples that consume the MCP server (athletic-analyst-ts/, athletic-analyst-py/).
  • docs/: Shared guides (e.g., CODE_STANDARDS.md) plus repo-wide references.

Build, Test, and Development Commands

  • cd mobile && fvm flutter pub get installs dependencies pinned by .fvmrc.
  • cd mobile && fvm flutter run launches the app on the active device.
  • cd mobile && ./scripts/checks.sh formats + analyzer + metrics; run before every PR.
  • cd mobile && ./scripts/integration_test.sh executes the MCP integration flow end-to-end.
  • cd mobile && ./scripts/clean_up.sh cleans, refetches deps, regenerates build_runner + l10n outputs after model or copy changes.
  • cd landing && firebase serve --only hosting --port 5000 previews updates; ./scripts/build-css.sh bundles CSS when needed.
  • cd mcp-server && npm install && npm start starts the standalone server or npm run install-global to expose the CLI.
  • cd examples && ./scripts/repo.sh help lists setup/build/integration commands for both examples.
  • cd examples/athletic-analyst-ts && npm install && npm run build prepares the TypeScript example.
  • cd examples/athletic-analyst-py && python3 -m venv .venv && .venv/bin/pip install -r requirements.txt prepares the Python example.

Coding Style & Naming Conventions

  • Follow docs/CODE_STANDARDS.md: two-space indent, fvm dart format, clean fvm flutter analyze.
  • Use English identifiers (lowerCamelCase members, UpperCamelCase types) and package: imports under lib/.
  • Localize UI strings via lib/l10n/intl_en.arb, regenerate with flutter gen-l10n, avoid hardcoded copy.
  • Use the shared Logger, prefer const/final, and rely on design system colors.

Read the full file on GitHub · 46 lines

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. 6d ago First seen · 46 lines · 849 tokens per session scan A 157f2d15ba45

Subscribe to this mod's changes

vytalLink AGENTS.md is an instructions file published in the GitHub repository xmartlabs/vytalLink (9 stars, last pushed 4mo ago), licensed MIT. It adds 849 tokens to every session, about $0.0042 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens