archi-context-fetch

archi-context-fetch is a skill for Claude Code, Codex from JiuNian3219/architext. It costs 38 tokens per session (2,440 once invoked), scanned A, original, MIT.

A helper that finds the smallest relevant set of Architext documentation files after an intent summary is created. It returns facts and notes missing information for another process to use.

In plain words
What is it for?
Use it before Architext protocol tasks, such as changing or editing a project, to gather the relevant documentation context.
Why use it?
It reduces the amount of documentation that must be read and keeps this lookup step separate from making changes or decisions.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it before Architext protocol tasks, such as changing or editing a project, to gather the relevant documentation context.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jiunian3219/architext/archi-context-fetch
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.

Any agent
npx skills add JiuNian3219/architext --skill archi-context-fetch
Clone the repo
git clone --depth 1 https://github.com/JiuNian3219/architext

Made for: Claude Code, Codex.

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 archi-context-fetch

README.md
[![agentmods](https://agentmods.dev/badge/skills/jiunian3219/architext/archi-context-fetch/github.svg)](https://agentmods.dev/skills/jiunian3219/architext/archi-context-fetch)
Your own site
<a href="https://agentmods.dev/skills/jiunian3219/architext/archi-context-fetch"><img src="https://agentmods.dev/badge/skills/jiunian3219/architext/archi-context-fetch/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for archi-context-fetch

Your own site · 80×15
<a href="https://agentmods.dev/skills/jiunian3219/architext/archi-context-fetch"><img src="https://agentmods.dev/badge/skills/jiunian3219/architext/archi-context-fetch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,440 The whole file, excluding the scripts and references it only reads on demand.
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.00038 $0.02440
Opus 5.5 $0.00015 $0.00976
Sonnet 5.5 $0.00008 $0.00488
Haiku 4.5 $0.00004 $0.00244

Measured 1mo ago against content hash 7f7ee0ad51a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

archi-context-fetch 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 1mo 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.

templates/en/skills/archi-context-fetch/SKILL.md · 253 lines

How it starts

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

Invocation

  • Auto-invoke: Yes, called by 00_system.md Front Pipeline.
  • Trigger location: Before user request enters protocol routing.
  • Execution context: When subagent supported must execute in independent subagent/independent context; only fallback to NO-SUBAGENT / NO-SKILL inline execution when no subagent.
  • Boundary: Only produce structured intermediate artifacts, does not execute protocols, does not modify project files.

Architext Context Fetch

Purpose

Read minimally necessary Architext documents based on Intent Card, produce structured Context Pack. This Skill is "librarian", only responsible for finding files, extracting facts, marking gaps; does not read product source code, does not modify files, does not execute commands, does not make final decisions for protocol.

Inputs

  • intent_card: archi-intent-normalizer output.
  • protocol_hint: Protocol about to load, e.g. /archi.change or change/edit.
  • known_state: Lightweight state known to caller, e.g. project features, task id, current discussion file.
  • available_files: Optional. Architext file list already discovered by caller.

Output Contract

Only output one JSON code block, no explanatory body text.

Continuation Contract: This Skill output is only Front Pipeline step 2. After the main agent receives the Context Pack, if missing_or_stale is empty or contains only non-blocking notes, it must continue to load and execute the protocol pointed to by next_context_action / Intent Card; do not treat the Context Pack as the final reply.

risk_flags are later protocol Gate inputs, not Front Pipeline stop markers. Stop to explain to the user only when missing_or_stale explicitly blocks execution, clarification is required, or a safety Gate must be shown first.

{
  "context_pack_version": 1,
  "for_intent": "change.edit",
  "target": {
    "task_id": null,
    "task_dir": null,
    "files": [],
    "refs": []
  },
  "must_read": [],
  "optional_read": [],
  "already_read": [],
  "relevant_facts": [
    {
      "source": "global/roadmap.json",
      "fact": "<fact directly usable for execution>",
      "confidence": 0.0
    }
  ],
  "missing_or_stale": [],
  "risk_flags": [],
  "do_not_read": [],
  "next_context_action": "<continue loading protocol / ask first / fill gap first>"
}

Read the full file on GitHub · 253 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. 1mo ago First seen · 253 lines · 38 tokens per session scan A 7f7ee0ad51a1

Subscribe to this mod's changes

archi-context-fetch is a skill published in the GitHub repository JiuNian3219/architext (14 stars, last pushed 5mo ago), licensed MIT. It adds 38 tokens to every session and 2,440 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories