Doc Coauthoring
aws-samples/sample-strands-agent-with-agentcore
Guide users through a structured workflow for co-authoring documentation.
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
Install Agreement
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreement --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/agreement .claude/skills/agreement && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .claude/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreementType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreement --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/agreement .agents/skills/agreement && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .agents/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreement --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/agreement .cursor/skills/agreement && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .cursor/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/AlpacaLabsLLC/skills-for-architects.git --path skills/agreement--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreement --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/agreement .gemini/skills/agreement && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .gemini/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreementInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/agreement .github/skills/agreement && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .github/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install AlpacaLabsLLC/skills-for-architects agreement --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architects.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/agreement .opencode/skills/agreement && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agreement" agent skill from https://github.com/AlpacaLabsLLC/skills-for-architects/tree/main/skills/agreement into .opencode/skills/agreement/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agreement", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agreement- GitHub stars
- 373
- Token cost
- ~959 tokens
- SKILL.md length
- 420 words
- Files
- 5
- Skills in repo
- 60
- Repo updated
- First seen
- Licence
- MIT
At a glance
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
- Tasks that involve Proposals and quotes
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Agreement is an agent skill from AlpacaLabsLLC/skills-for-architects. Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files (for example `README.md`, `host-contract.json` and `templates/AGREEMENT.md`).
It sits in Sales & Support, covering Proposals and quotes. The repository describes itself as: Claude Code skills for architecture, real estate, and workplace strategy. Type /skill-name and go. The licence is MIT.
When your agent uses it
- Tasks that involve Proposals and quotes
Example prompts
- “/agreement”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
What it can do on your machine
Read from SKILL.md and the folder at commit 657bfd5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGlobGrepBashAskUserQuestion
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agreement loads about 959 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 420 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from AlpacaLabsLLC/skills-for-architects at commit 657bfd5, republished under its MIT licence (© AlpacaLabsLLC). 420 words, ~959 tokens.
Download SKILL.mdSave it as
.claude/skills/agreement/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- agreement
- description
- Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
- allowed-tools
- Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion
/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.
<!-- architecture-studio:harness-compatibility -->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.
Show full SKILL.md (158 more words)Show less
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.
© AlpacaLabsLLC, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files in skills/agreement of AlpacaLabsLLC/skills-for-architects.
- SKILL.md
- README.md
- host-contract.json
- templates/AGREEMENT.md
- templates/amendment.md
Open the folder on GitHubat commit 657bfd5
Compare with similar skills
Agreement next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agreement this skillAlpacaLabsLLC/skills-for-architects | 373 | — | ~959 | Automated safety check: Notes | MIT | |
| Doc Coauthoringaws-samples/sample-strands-agent-with-agentcore | 195 | 40 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Audit Onboarding Proposalhoangnb24/repository-harness | 1.2k | — | ~4k | Automated safety check: Pass | MIT | |
| No Negative EchoLB623/no-negative-echo | 900 | — | ~965 | Automated safety check: Pass | MIT | |
| GEO Service Proposal Generatorzubair-trabzada/geo-seo-claude | 11k | — | ~3k | Automated safety check: Notes | MIT | |
| Architectural ProposalsFritzAndFriends/SharpSite | 145 | 2 repos | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
- Official
Audit Onboarding Proposal
hoangnb24/repository-harness
Use only when the user explicitly invokes $audit-onboarding-proposal.
No Negative Echo
LB623/no-negative-echo
Prevent 此地无银三百两式 residue: finalize artifacts without echoing rejected session-only alternatives into labels, metadata, commits, PRs, or handoffs.
GEO Service Proposal Generator
zubair-trabzada/geo-seo-claude
Builds a client-ready AI-search-optimization proposal from an existing GEO audit, with pricing tiers, an ROI estimate and a markdown document ready to send.
Architectural Proposals
FritzAndFriends/SharpSite
How to write comprehensive architectural proposals that drive alignment before code is written
Counter Proposal Generator
zubair-trabzada/ai-legal-claude
Generates specific counter-proposals for every unfavorable clause, with replacement language, negotiation talking points, and a ready-to-send email template
More from AlpacaLabsLLC/skills-for-architects
All 60 skills in this repoColor Palette Generator
AlpacaLabsLLC/skills-for-architects
Create an HTML color palette from a mood, description, or image, with swatches, color codes, pairings, and contrast checks.
Demographics Analysis
AlpacaLabsLLC/skills-for-architects
Research population, income, age, housing, and employment around a site.
Environmental Analysis
AlpacaLabsLLC/skills-for-architects
Research climate, sun, flood, seismic, soil, contamination, and topography for a site.
Mobility Analysis
AlpacaLabsLLC/skills-for-architects
Research transit, walking, cycling, pedestrian infrastructure, and airport access for a site.
Product Data Cleanup
AlpacaLabsLLC/skills-for-architects
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting.
Product Enrich
AlpacaLabsLLC/skills-for-architects
Enrich FF&E schedule rows with categories, colors, materials, and style tags.
Related
Categories
Questions about Agreement
What does Agreement do?
Maintain sourced agreement context and scope in PROJECT.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow. Agreement is an agent skill from AlpacaLabsLLC/skills-for-architects.md, cite registered contracts/proposals, and record amendments without imposing a commercial workflow.
When should I use Agreement?
Agreement fits situations like: tasks that involve Proposals and quotes.
How do I install Agreement in Claude Code?
Run `npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a claude-code`. Or copy the skill folder (skills/agreement in AlpacaLabsLLC/skills-for-architects) into .claude/skills/agreement in your project. Claude Code loads it when a task matches its description.
How do I install Agreement in Codex?
Run `npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a codex`. Or copy the skill folder (skills/agreement in AlpacaLabsLLC/skills-for-architects) into .agents/skills/agreement in your project. Codex loads it when a task matches its description.
Can I use Agreement in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AlpacaLabsLLC/skills-for-architects --skill agreement -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agreement, .gemini/skills/agreement, .github/skills/agreement and .opencode/skills/agreement in your project.
What does Agreement need to run?
SKILL.md names no scripts, command-line tools or credentials: Agreement is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash, AskUserQuestion.
Does Agreement access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Agreement safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Agreement use?
Agreement is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agreement use?
About 959 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Agreement?
Skills that share tags, products or a category with Agreement: Doc Coauthoring (aws-samples/sample-strands-agent-with-agentcore, 195 stars), Audit Onboarding Proposal (hoangnb24/repository-harness, 1.2k stars), No Negative Echo (LB623/no-negative-echo, 900 stars) and GEO Service Proposal Generator (zubair-trabzada/geo-seo-claude, 11k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agreement?
AlpacaLabsLLC (a GitHub organization) maintains it in AlpacaLabsLLC/skills-for-architects, which has 373 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 5, 2026.
Source: AlpacaLabsLLC/skills-for-architects on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.