Agreement

Organization

AlpacaLabsLLC

agreement

Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.

Overview

Publisher	AlpacaLabsLLC
Repository	`skills-for-architects`
Skill name	`agreement`
Stars	386
Forks	81
Bundled files	3
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
3 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by AlpacaLabsLLC on GitHub. Read the source before you install it.

Installation

Install the Agreement AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git /tmp/skills-for-architects
mkdir -p .claude/skills
cp -r /tmp/skills-for-architects/skills/agreement .claude/skills/agreement

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Agreement in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Agreement on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Agreement is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

/as:agreement

Before acting, read the host contract, this component's declaration (skill:agreement), and applicable workspace semantics. Load only the required modes from the shared catalog.

Use the host adapter and available native tools or ordinary task-specific code. Operation names identify the semantic work in the workspace model, not installed functions or a script API. Resolve canonical context before durable work. No Arch Studio runner, package installation or executable reconstruction is required. Existing exact authorization persists; ask only for material missing information or missing permission.

Own only the bounded Agreement section in PROJECT.md plus authored agreement/contract documents. Project owns other facts; studio owns registration/status. Register supplied signed agreements, SOWs and amendments through receive; never overwrite a prior agreement document.

Before changing records

Before persistent changes, follow the native mutation sequence: Inspect → Prepare → Verify preparation → Apply → Verify result → Complete. Inspect pending work first. Finish and verify preparation before the first canonical write: separately reread every saved original and prepared file, check its complete actual bytes, establish durable saving, and inspect actual permissions, ownership and ACLs. Merely writing recovery files does not finish verification. Apply only that verified set. Mark complete only after fresh readback validates the entire affected result and its relationships. Read-only requests and inline drafts need no publication sequence.

Agreement context edits affect only the bounded PROJECT.md section; retain the complete original/prepared PROJECT.md and guard the cited registered document bytes, raw hash and applicable terms seal. Registering an authored agreement or amendment affects that document plus DOCUMENTS.csv before any optional, separately authorized context update. A cited source is not permission to edit it.

agreement.init creates the bounded context from a registered agreement/contract ID. agreement.promote is optional for an accepted sealed proposal and cites its ID, content hash and issued-terms hash without duplicating the proposal. Direct engagements do not require a proposal. Facts have field/value/source/date; preserve unknowns, and interpret clauses through the harness and applicable originals rather than deterministic scope classification.

The section contains parties/term/fees/caps and exactly the scope headings In scope, Not in scope and Requires SOW when supplied. check reads those source-linked bullets and presents advisory in-scope/needs-SOW/out-of-scope findings; the user decides. No status or automatic invoice gate is introduced.

agreement.record-amendment cites a registered agreement/contract ID, explicit date and summary. Preview any associated fact/scope changes separately when not already authorized; retain prior evidence. agreement.verify checks cited documents. A malformed section, missing document or checksum conflict blocks dependent mutation and remains preserved. Reopen PROJECT.md and cited originals after the action. Legal interpretation or execution status is not established by a successful registration.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Agreement AI skill do?

Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.

Why use Agreement on TypingMind?

Because you install it once and use it with any model. Agreement is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Agreement in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Agreement?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Agreement?

As many as you like. As long as a model supports skills, you can use Agreement with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Agreement AI skill free?

Yes. It is published on GitHub by AlpacaLabsLLC under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Html Ppt Zhangzara Cartesian

nexu-io

OrganizationPopular

An economics senior thesis on the employment effects of local minimum-wage increases — identification strategy, evidence, and limitations. Built as a decision-grade coursework defense deck for thesis…

Constraint Driven Development

addyosmani

CommunityPopular

Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no…

Spec Driven Development

addyosmani

CommunityPopular

Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and…

Ramp

Fetch and follow Ramp's published agent playbooks inside Paperclip, with mandatory approval gates for spend, incorporation, cards, account setup, and other financial actions.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

/as:agreement

Before changing records

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now