trackly-cli AGENTS.md

Project instructions for Trackly CLI, a Node.js command-line program and MCP server that provides access to job listings.

In plain words
What is it for?
They are for understanding the codebase, using its commands, and avoiding forbidden changes to the live backend or database.
Why use it?
They give coding agents the project structure, safe production boundaries, and development conventions needed to change the repository correctly.

Instructions file for CodexOpenCode

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/trackly-app/trackly-cli/agents-md
Clone the repo
git clone --depth 1 https://github.com/trackly-app/trackly-cli

Made for: Codex, OpenCode.

Per session 1,862 This file is loaded in full into every session.
When invoked 1,862 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.01862 $0.01862
Opus 5 $0.00931 $0.00931
Sonnet 5 $0.00372 $0.00372
Haiku 4.5 $0.00186 $0.00186

Measured yesterday against content hash 017193bc2a09, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

trackly-cli 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.

AGENTS.md · 119 lines

How it starts

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

AGENTS.md - trackly-cli

Universal context for AI coding agents (Codex, Cursor, Copilot, Claude Code, Devin, Jules, etc.)

Project Overview

  • Product: Trackly CLI + MCP Server — terminal access to 170K+ jobs across 3,800+ companies
  • Stack: Node.js 20+ / plain CommonJS JavaScript (no TypeScript, no build step)
  • Package: npm install -g trackly-cli (public npm package)
  • Backend API: https://closeai.mba (same as Close AI — do NOT modify the backend from this repo)
  • Backend production source of truth: after the 2026-06-30 Azure cutover, https://closeai.mba is served by Azure and the live DB is Azure blue Postgres behind the backend/VNet. This CLI repo is a consumer only; do not use AWS RDS, Render, old DB aliases, ssh closeai-web, or direct SQL for live production claims, migrations, user exports, or company-add decisions.
  • Repo: Public GitHub — trackly-app/trackly-cli

Architecture

bin/trackly          # CLI entrypoint (shebang script). All commands + arg parser + main()
lib/client.js        # HTTP client: config loading, token refresh, apiRequest()
lib/formatters.js    # Terminal output: color(), outputJobs(), outputCompanies(), etc.
mcp/server.js        # MCP server entrypoint and search/network tools, launched via `trackly mcp`
mcp/apply-tools.js   # Trackly Apply MCP schemas, validators, and tool registration
docs/trackly-tools.md  # MCP tool reference (for embedding in AI agent contexts)
docs/solutions/       # documented solutions organized by category with searchable YAML frontmatter (module, tags, problem_type)
CONCEPTS.md           # shared domain vocabulary for entities, named processes, and status concepts
server.json          # MCP Registry manifest (io.github.trackly-app/trackly)

Dev Commands

# No build step — pure JS
node bin/trackly --help        # Run locally without installing
npm link                       # Symlink for local dev

There is a small Node test suite (npm test), no linter, and no build step. The package ships raw JS.

Read the full file on GitHub · 119 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. yesterday First seen · 119 lines · 1,862 tokens per session scan A 017193bc2a09

Subscribe to this mod's changes

trackly-cli AGENTS.md is an instructions file published in the GitHub repository trackly-app/trackly-cli (3 stars, last pushed 3d ago), licensed MIT. It adds 1,862 tokens to every session, about $0.0093 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.