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 skills add ilang-ai/autocode --skill seegit clone --depth 1 https://github.com/ilang-ai/autocodeWrote 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.
[](https://agentmods.dev/skills/ilang-ai/autocode/see)<a href="https://agentmods.dev/skills/ilang-ai/autocode/see"><img src="https://agentmods.dev/badge/skills/ilang-ai/autocode/see/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.
<a href="https://agentmods.dev/skills/ilang-ai/autocode/see"><img src="https://agentmods.dev/badge/skills/ilang-ai/autocode/see.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00732 |
| Opus 5.5 | $0.00000 | $0.00293 |
| Sonnet 5.5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
see 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.
What it actually says
see — S1: understand what they want, in their words
[PROTOCOL:iLang|v=5.0|layer=declaration]
::PRIOR{dimension:completion|default:assume_incomplete|authority:system|scope:@JOURNEY} ::PRIOR{dimension:execution|default:act_when_safe|authority:system|scope:@JOURNEY}
::GENE{see|conf:confirmed|scope:global} T:classify_intent_silently|create|change|fix|question|default=create T:detect_level_from_first_3_messages|default=beginner T:zero_jargon_for_beginners|light_for_intermediate|full_technical_for_advanced T:detect_user_language_respond_same T:accept_a_pointer_not_a_spec|url|product_name|their_own_screenshot|⇒product-study T:size_the_task|small<30min=build_direct|medium<2hr=brief_plan|large>2hr=plan T:fill_goal_header|who_is_it_for|the_one_job T:ask_at_most_one_question|when:goal_header_unfillable|yes_no_or_plain T:confirmed_requirements_are_locked|ask_before_changing_them T:take_initiative|never_wait_for_direction A:announce_the_classification⇒never A:say_large_project_to_a_beginner⇒say_we_do_it_in_steps A:ask_for_a_feature_list⇒infer_then_cut A:silently_change_a_locked_requirement⇒ask_first A:scope_creep⇒flag_in_one_line A:over_explain⇒confuse A:assume_knowledge⇒alienate
::ACTIVATE{see} ON:every_message ON:new_task ON:requirement_confirmed
::STATE{@INTENT, what the person wants, in one sentence they would sign} ::STATE{@LEVEL, beginner | intermediate | advanced}
[SCAN:@SRC|typ=intent]=>[CLSF:@INTENT|typ=silent]=>[DECI:@LEVEL|src=first_3_messages]=>[PLAN:@SCOPE|typ=small_medium_large]=>[Ω:@USER|fmt=text|lim=1]
::EVIDENCE{id:see1|deliverable:intent|kind:text|ref:goal_header|verified_by:@USER|result:they_said_yes_or_crossed_out}
::SAY{@AUTOCODE→@USER}{ user: "帮我做一个网站" ⇒ beginner, create, small-medium; no jargon, no code in chat user: "用 React 做" ⇒ intermediate; light technical, brief explanations user: "Go 写个 gRPC 服务" ⇒ advanced; full technical, skip explanations user: "我想要一个像 Linear 的" ⇒ pointer, not a spec ⇒ product-study first output: "这个我们分几步来做，今天先把核心功能跑通。" }
Powered by iLang v5.0 | ilang.ai
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 Changed 69a027f4cb2b
- 8d ago Changed 13e9f16f69a2
- 9d ago First seen · 54 lines · 0 tokens per session scan A 662666a6e1f2
see is a skill published in the GitHub repository ilang-ai/autocode (104 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 732 tokens. 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-10-15.
Other skills, from other repositories
mckinsey-consultant
A consulting style method for breaking business questions into structured analyses and producing research reports or presentations.
ast-grep
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for…
mimeng-writing
A Chinese-language writing guide for creating highly clickable articles about emotions, stories, and social issues. It covers titles, openings, emotional engagement, memorable lines, and narrative structure.
us-gov-shutdown-tracker
Track and analyze US government shutdown liquidity impacts by monitoring TGA (Treasury General Account), bank reserves, EFFR, and SOFR data from FRED API. Use when user wants to (1) analyze current or past government shutdown effects on financial markets, (2) track liquidity conditions during fiscal policy…
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm…
screenpipe
Search screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.