cotend-semantic-alignment

cotend-semantic-alignment is a skill for Codex from lhh1301506137/CoTend. It costs 263 tokens per session (8,537 once invoked), scanned B, original, Apache-2.0.

A process for making sure an AI and a product team share the same understanding of what a project or feature should mean.

In plain words
What is it for?
Use it to establish, rebuild, or update the meaning of a project or feature and record the agreed understanding for later work.
Why use it?
It helps correct misunderstandings about the intended product before implementation details are changed.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to establish, rebuild, or update the meaning of a project or feature and record the agreed understanding for later work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lhh1301506137/cotend/cotend-semantic-alignment
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 lhh1301506137/CoTend --skill cotend-semantic-alignment
Clone the repo
git clone --depth 1 https://github.com/lhh1301506137/CoTend

Made for: 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 cotend-semantic-alignment

README.md
[![agentmods](https://agentmods.dev/badge/skills/lhh1301506137/cotend/cotend-semantic-alignment/github.svg)](https://agentmods.dev/skills/lhh1301506137/cotend/cotend-semantic-alignment)
Your own site
<a href="https://agentmods.dev/skills/lhh1301506137/cotend/cotend-semantic-alignment"><img src="https://agentmods.dev/badge/skills/lhh1301506137/cotend/cotend-semantic-alignment/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 cotend-semantic-alignment

Your own site · 80×15
<a href="https://agentmods.dev/skills/lhh1301506137/cotend/cotend-semantic-alignment"><img src="https://agentmods.dev/badge/skills/lhh1301506137/cotend/cotend-semantic-alignment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 263 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,537 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00263 $0.08537
Opus 5.5 $0.00105 $0.03415
Sonnet 5.5 $0.00053 $0.01707
Haiku 4.5 $0.00026 $0.00854

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

Security

Grade B, and why

cotend-semantic-alignment scanned grade B with 1 finding 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/semantic-contract.mjs), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Subtle steeringmediumPrompt injection

Instructions that bias recommendations or shape behaviour without the user noticing.

| `semantic_change` | The user knowingly wants to change confirmed product meaning or a candidate route materially changes L0-L2. | Show before/after/route impact, confirm, supersede old meaning, propagate affected work,
skills/cotend-semantic-alignment/SKILL.md · 493 lines

How it starts

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

CoTend Semantic Alignment

Companion version: cotend-collaboration-v2.01

Align product meaning before implementation details. Preserve one Plan Tree and its linked truth files; do not create a second semantic tree.

Before showing or writing user-facing governance prose, consume Project Init's persisted user_facing_language_resolution from STATUS.md or the mapped equivalent. When it is absent, invalid, or conflicting, delegate only Project Init's User-Facing Governance Language Resolution subsection to that sole owner, persist or return its result, and then continue or stop accordingly. Do not run full Init/Auto Mode, copy the source order here, infer from the conversation/repository/host, or create a competing record. This narrow delegation preserves the direct entry and does not give Init semantic-alignment authority. Full and Adaptive use the same language result. Packet headings below are an illustrative rendering; render them to the resolved normalized_tag without changing fields or authority semantics.

Independent Entry And Minimum Truth

Invoke this Skill directly. Do not run or require cotend-init or full cotend-project-init Auto Mode first; the sole-language-resolver delegation above is the only preparatory exception.

Read only the minimum project truth needed for the requested scope, in this order:

  1. the user's current request and latest explicit decisions;
  2. the binding active Plan Tree/task specification when current workflow evidence says CoTend governance is active;
  3. existing active STATUS.md, PRD/brief, PROJECT-PLAN-TREE.md, target node/understanding docs, and relevant decision/knowledge records;
  4. representative product behavior, code, tests, or UI needed to compare intended and actual meaning.

The presence of STATUS.md#cotend_workflow alone does not make stale task state binding. Missing Plan Tree or understanding records are not an Init prerequisite and do not block this Skill. Classify the request as new_baseline, then create or update the minimum canonical Plan Tree/understanding/decision surfaces only after the required L0-L2 confirmation. Never create a second truth tree.

Read the full file on GitHub · 493 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 493 lines · 263 tokens per session scan B 97a4e46d16ac

Subscribe to this mod's changes

cotend-semantic-alignment is a skill published in the GitHub repository lhh1301506137/CoTend (2 stars, last pushed 7d ago), licensed Apache-2.0. It adds 263 tokens to every session and 8,537 once invoked, about $0.0011 per session on Opus 5.5. A static security scan graded it B with 1 finding (subtle steering). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

extension-creator

Create AiderDesk extensions by setting up extension files, defining metadata, implementing Extension interface methods, and updating documentation. Use when building a new extension, creating extension commands, tools, or event handlers.

hotovo/aider-desk · 44 tokens

agent-creator

Create and configure AiderDesk agent profiles by defining tool groups, approval rules, system prompts, subagent settings, subagent filtering, and provider/model selection. Use when setting up a new agent, creating a profile, or configuring agent tools, permissions, and subagent behavior.

hotovo/aider-desk · 60 tokens

writing-tests

Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.

hotovo/aider-desk · 48 tokens

deep-review

Comprehensive code review — architecture + correctness. Scope with args — diff (default), branch, all, path, or IDE selection. Delegates to reviewer agent for large scope.

zahardev/aicontext · 39 tokens

review

Review code changes for bugs, security, edge cases. Scope with args — diff (default), branch, commit, path, or IDE selection. Delegates to reviewer agent for large scope.

zahardev/aicontext · 40 tokens

align-context

Update all context files (task, spec, task-context, worklog) to reflect current state of work — fixes stale entries, fills missing knowledge, reports what changed.

zahardev/aicontext · 36 tokens