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 bitrise-io/agent-skills --skill using-bitrise-cigit clone --depth 1 https://github.com/bitrise-io/agent-skillsWrote 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/bitrise-io/agent-skills/using-bitrise-ci)<a href="https://agentmods.dev/skills/bitrise-io/agent-skills/using-bitrise-ci"><img src="https://agentmods.dev/badge/skills/bitrise-io/agent-skills/using-bitrise-ci/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/bitrise-io/agent-skills/using-bitrise-ci"><img src="https://agentmods.dev/badge/skills/bitrise-io/agent-skills/using-bitrise-ci.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.00127 | $0.04758 |
| Opus 5.5 | $0.00051 | $0.01903 |
| Sonnet 5.5 | $0.00025 | $0.00952 |
| Haiku 4.5 | $0.00013 | $0.00476 |
Grade A, and why
using-bitrise-ci 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Bitrise CI
Contents
- Tools (Authentication, MCP, API, CLI)
- Core concepts
- Creating projects
- Working with bitrise.yml (Structure, Components, Docker Containers)
- Troubleshooting builds
Automated access
Authentication
An access token is required to interact with Bitrise in automated ways (API, MCP etc.). Users can create a personal or workspace access token. It should be stored securely.
MCP server
The Bitrise MCP server is available online at https://github.com/bitrise-io/bitrise-mcp, or it can be run locally. It requires authentication with a token using the Authorization: Bearer {token} header. When the MCP server is available, prefer it to the API or other tools.
API
The Bitrise REST API allows managing various Bitrise resources. The detailed reference is available here. The API requires authentication with a PAT with the Authorization: {PAT} header (without Bearer).
CLI
Bitrise CLI is useful when working on a local environment. It doesn't interact with Bitrise resources, but helps with editing and validating bitrise.yml, and allows running workflows locally. It supports Mac and Linux.
To install, use brew install bitrise or check the Releases page for other options.
Local runs expect bitrise.yml at the root of the working directory, with an optional .bitrise.secrets.yml containing sensitive inputs.
Common commands:
# Output the list of available commands
bitrise help
# Start local workflow editor UI
bitrise :workflow-editor
# Validate bitrise.yml
bitrise validate -c {config_path}
# List available workflows
bitrise workflows
# Run a workflow locally
bitrise run {workflow_id}
What ships with it
1 file 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.
- 2mo ago First seen · 482 lines · 127 tokens per session scan A 1c12e704baea
using-bitrise-ci is a skill published in the GitHub repository bitrise-io/agent-skills (5 stars, last pushed 7mo ago), licensed MIT. It adds 127 tokens to every session and 4,758 once invoked, about $0.0005 per session on Opus 5.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-31.
using-bitrise-ci compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| using-bitrise-cibitrise-io/agent-skills | Skill | 5 | 7mo ago | MIT | A | 127 | Claude Code, Codex |
| chinese-git-workflowjnMetaCode/superpowers-zh | Skill | 8.5k | 12d ago | MIT | A | 69 | Claude Code |
| atmos-profilescloudposse/atmos | Skill | 1.4k | today | Apache-2.0 | A | 35 | Claude Code |
| webhook-managementhoangsonww/Claude-Code-Agent-Monitor | Skill | 1.2k | yesterday | MIT | A | 56 | Claude Code, Codex |
| monorepo-managementwshobson/agents | Skill | 42k | 2d ago | MIT | C | 54 | Claude Code |
| managing-github-actions-secretsPostHog/posthog-foss | Skill | 728 | today | MIT | A | 67 | Claude Code, Codex |
| postman-newman-automationLambdaTest/agent-skills | Skill | 391 | 2d ago | MIT | A | 156 | Claude Code, Codex |