valuecell AGENTS.md

Repository instructions for Python development in the ValueCell-ai/valuecell project. They describe the project’s package manager, virtual environment, testing command, import practices, and runtime-check preferences.

In plain words
What is it for?
Use them when writing Python code, choosing how to import names, running tests, or adding runtime validation in that repository.
Why use it?
They give coding agents consistent project rules and reduce avoidable problems with dependencies, imports, and type handling.

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/valuecell-ai/valuecell/agents-md
Clone the repo
git clone --depth 1 https://github.com/ValueCell-ai/valuecell

Made for: Codex, OpenCode.

Per session 1,224 This file is loaded in full into every session.
When invoked 1,224 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.01224 $0.01224
Opus 5 $0.00612 $0.00612
Sonnet 5 $0.00245 $0.00245
Haiku 4.5 $0.00122 $0.00122

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

Security

Grade A, and why

valuecell 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 · 160 lines

How it starts

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

Guidelines

Python Programming

Python Environment

  • Package manager: uv
  • Virtual environment: ./python/.venv
  • Testing command: uv run pytest

Imports

  • Avoid inline imports unless required to break a circular dependency.
  • If you import more than three names from a single module, prefer qualified imports:
    • Prefer: import pathlib; pathlib.Path, pathlib.PurePath
    • Avoid: from pathlib import Path, PurePath, PurePosixPath, ...
  • Postpone changes to __init__ and __all__ until APIs stabilize.
  • Use TYPE_CHECKING for imports only needed for type hints.
from typing import TYPE_CHECKING

if TYPE_CHECKING:
    from mypkg.schemas import AgentConfig

Runtime Checks

  • Avoid excessive use of getattr, hasattr, and runtime type checks.
  • If an object is a pydantic BaseModel, prefer using its validated attributes and type annotations instead of probing attributes at runtime.
  • Rely on pydantic validation, model validators, and type hints; prefer TypedDict or Protocol for structural typing when appropriate.
  • When runtime checks are necessary, make them explicit, minimal, and well-documented so the reason for the guard is clear.

Async-First Design

  • Prefer asynchronous APIs for I/O-bound work.
  • Use asyncio or anyio; for HTTP, prefer httpx (async client).
  • Ensure clear async boundaries: public APIs and I/O paths should be async.
  • Provide minimal sync adapters only when needed, and document them.
import asyncio
from loguru import logger
import httpx

async def fetch_agent_state(url: str, timeout_s: float) -> dict:
    """Fetch agent state from a remote endpoint."""
    async with httpx.AsyncClient(timeout=timeout_s) as client:
        resp = await client.get(url)
        resp.raise_for_status()
        data = resp.json()
        logger.info("Fetched state from {url}", url=url)
        return data

def fetch_agent_state_sync(url: str, timeout_s: float) -> dict:
    """Synchronous adapter. Prefer the async variant."""
    return asyncio.run(fetch_agent_state(url, timeout_s))

Read the full file on GitHub · 160 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 · 160 lines · 1,224 tokens per session scan A 33b2f7087c55

Subscribe to this mod's changes

valuecell AGENTS.md is an instructions file published in the GitHub repository ValueCell-ai/valuecell (11,006 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 1,224 tokens to every session, about $0.0061 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.