Sample Agent Skills for Builders is a collection of reusable skills that extend AI coding agents with AWS, CDK, security, testing, and engineering workflows. Developers can install the skills for practical AWS development tasks or use the repository as a model for creating their own agent skills. The catalogue entries are skills and instructions from this collection.
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 aws-samples/sample-agent-skills-for-builders --skill quip-to-gitlab-wikigit clone --depth 1 https://github.com/aws-samples/sample-agent-skills-for-buildersWrote 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/aws-samples/sample-agent-skills-for-builders/quip-to-gitlab-wiki)<a href="https://agentmods.dev/skills/aws-samples/sample-agent-skills-for-builders/quip-to-gitlab-wiki"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-skills-for-builders/quip-to-gitlab-wiki/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/aws-samples/sample-agent-skills-for-builders/quip-to-gitlab-wiki"><img src="https://agentmods.dev/badge/skills/aws-samples/sample-agent-skills-for-builders/quip-to-gitlab-wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00500 |
| Opus 5 | $0.00023 | $0.00250 |
| Sonnet 5 | $0.00009 | $0.00100 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
quip-to-gitlab-wiki 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 10d 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.
What it actually says
Quip to GitLab Wiki Migration
Migrate Quip documents to GitLab Wiki with full content and media preservation.
When to Apply
Reference this skill when:
- Migrating Quip documents to GitLab
- Converting documentation to wiki format
- Preserving embedded images and videos
- Setting up GitLab wiki structure
How It Works
- Gather Sources - Collect Quip URLs and tokens
- Convert - Transform Quip HTML to Markdown
- Push - Upload to GitLab Wiki
- Configure - Set up GitLab MCP for future edits
- Structure - Organize wiki navigation
Prerequisites
- Quip API token
- GitLab project with wiki enabled
- Python 3.8+ with html2text
- ffmpeg (for video compression)
Usage
# Convert Quip document (token from environment)
export QUIP_TOKEN="your_token_here"
python scripts/quip-to-markdown.py <thread_id> <output_dir>
# Push to GitLab wiki
./scripts/push-to-wiki.sh <wiki_git_url> <content_dir> <page_path> <quip_url>
Conversion Features
- HTML to Markdown via html2text
- Embedded image download
- Video compression (MOV→MP4 at 720p)
- Asset organization in
uploads/
Wiki Structure
wiki/
├── Home.md
├── Section-Name/
│ ├── _index.md
│ └── Page-Name.md
└── uploads/
├── image1.png
└── video1.mp4
Image Path Rules
| Page Location | Image Path |
|---|---|
| Root pages | uploads/image.png |
| Section pages | ../uploads/image.png |
| Nested pages | ../../uploads/image.png |
References
What ships with it
4 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.
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.
- 10d ago First seen · 79 lines · 45 tokens per session scan A 94044f8ea225
quip-to-gitlab-wiki is a skill published in the GitHub repository aws-samples/sample-agent-skills-for-builders (47 stars, last pushed 14d ago), licensed Apache-2.0. It adds 45 tokens to every session and 500 once invoked, about $0.0002 per session on Opus 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.
Other skills, from other repositories
pdf-processing
Extract text from PDFs, fill forms, and merge documents.
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
use-ifclite
Work with IFC / BIM files (.ifc, .ifcx, IFC2X3 / IFC4 / IFC4X3 / IFC5) from the terminal using the ifc-lite CLI — inspect, query, validate (IDS), export (CSV/JSON/IFC/glTF/Parquet), create elements, merge, convert schema versions, diff, clash-check, run BCF collaboration, and script the SDK. Use whenever a task…
pdf-processing
Extract text and tables from PDF files, fill forms, merge documents. Use when working with PDF files or when the user mentions PDFs, forms, or document extraction.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…