Skills agentix-ceo
📦
agentix-ceo
v1.2.0 Content revision r2 Critical ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables
Orchestrate Agentix AI Teams
Coordinating several AI workers can make roles, tasks, and progress difficult to track. This skill manages Agentix teams through a structured API workflow.
Supports: Claude Codex Code(CC)
Do not auto-install this skill.
The canonical policy requires operator review before any installation action.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "agentix-ceo" from https://skillstore.io/skills/agentix-cloud-agentix-ceo.md and its manifest at https://skillstore.io/api/skills/agentix-cloud-agentix-ceo/manifest. Verify the artifact. Do not auto-install. Inspect the skill and report your findings, then wait for an operator or manual installation decision.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "agentix-ceo". Show my current team status without changing anything.
Expected outcome:
- Team summary with its goal, current playbook mode, and configured roles.
- Active worker list with assigned tasks and current statuses.
- Recent event summary highlighting completed, failed, and blocked work.
Using "agentix-ceo". Launch one backend worker for the approved authentication task.
Expected outcome:
The approved task is assigned to the existing backend role. One worker is launched, and its current status is reported.
Using "agentix-ceo". Recommend a guarded plan for the ready backlog.
Expected outcome:
The response groups tasks by role, identifies dependencies, proposes a concurrency limit, and marks merges or credential changes for approval.
Security Audit
Criticalv5 • 7/23/2026 Open versioned report
Most external-command alerts are false positives caused by Markdown backticks, while Agentix endpoint references are intentional network behavior. The skill collects high-value credentials, transmits them to Agentix, and follows remotely fetched playbooks. Unauthenticated self-hosting and autonomous worker mode add further operational risk.
1
Files scanned
266
Lines analyzed
36
Review items
0
False positives ignored
Confirmed security concerns (4)
Critical
Third-Party Credential Collection
The skill asks users for Anthropic and GitHub tokens, then places them in Agentix team configuration. These secrets can enable model spending and repository access.
The instructions explicitly request both credentials and show them as fields sent to Agentix API resources.
High
Untrusted Remote Playbook Controls Agent Behavior
The skill fetches a remote team playbook and applies its modes, policies, and custom rules. Compromised remote content could steer privileged agent actions.
The file explicitly requires fetching, applying, preserving, and updating remotely stored operating instructions.
High
Unauthenticated Self-Hosted Control API
The self-hosted path states that its API has no authentication and is open on the local network. Other local-network users could control teams and workers.
The instructions explicitly describe the self-hosted API as open on the local network with no authentication.
High
Autopilot Permits Unbounded Autonomous Changes
Autopilot authorizes continuous planning, task creation, worker spawning, review, and merge activity. Missing budgets and approval gates could cause uncontrolled changes or spend.
The documented mode grants full autonomy and continuous looping without defining concurrency, cost, or merge limits.
Capability review items (36)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
High
Hidden file in home directory
On every session start, check `~/.agentix/credentials`:
The skill explicitly checks a hidden credentials file in the user's home directory at every session start, creating persistent access outside the workspace.
High
Hidden file in home directory
mkdir -p ~/.agentix && cat > ~/.agentix/credentials << 'EOF'
The shell example creates a hidden home directory and writes an Agentix API key to a plaintext credentials file.
High
Hidden file in home directory
mkdir -p ~/.agentix && cat > ~/.agentix/credentials << 'EOF'
The shell example creates a hidden home directory and persists self-hosted connection settings outside the workspace.
High
Hidden file in home directory
If credentials are already loaded from `~/.agentix/credentials`, skip to [Playbook](#playbook).
The instruction depends on loading values from the hidden home credentials file, confirming persistent filesystem access.
High
Hidden file in home directory
Save the returned `apiKey` and `customerId` to `~/.agentix/credentials` immediately. Do not display
The skill directs the agent to write a newly issued API key and customer identifier into the hidden home credentials file.
High
Hidden file in home directory
Reuse the same team across sessions. Do not create a new team each time. Save the returned `teamId`
The skill directs the agent to persist the returned team identifier in the hidden home credentials file for reuse.
High
Git platform tokens
{ "config": { "gitRepoUrl": "https://github.com/org/repo", "githubToken": "$GITHUB_TOKEN" } }
The skill asks for a GitHub token and places it in Agentix team configuration, exposing a repository credential to another service.
High
Generic API/secret keys
API_KEY=at_live_...
Although the displayed value is a placeholder, the example instructs the agent to persist a live Agentix API key in plaintext.
High
Generic API/secret keys
Authorization: Bearer $API_KEY
The instruction uses the Agentix API key as a bearer credential in a request to create a remote team.
High
Generic API/secret keys
Authorization: Bearer $API_KEY
The instruction sends the Agentix API key as bearer authorization while updating remote team configuration.
High
Generic API/secret keys
{ "anthropicApiKey": "$ANTHROPIC_API_KEY" }
The request body transmits the user's Anthropic API key into Agentix team configuration.
High
Generic API/secret keys
Authorization: Bearer $API_KEY
The instruction sends the Agentix API key as bearer authorization while replacing the remote playbook.
High
Generic API/secret keys
{ "anthropicApiKey": "$ANTHROPIC_API_KEY" }
The configuration example transmits the user's Anthropic API key to Agentix for worker execution.
Medium
Hidden file access
On every session start, check `~/.agentix/credentials`:
The skill explicitly checks a hidden credentials file in the user's home directory at every session start, creating persistent access outside the workspace.
Medium
Hidden file access
mkdir -p ~/.agentix && cat > ~/.agentix/credentials << 'EOF'
The shell example creates a hidden home directory and writes an Agentix API key to a plaintext credentials file.
Medium
Hidden file access
mkdir -p ~/.agentix && cat > ~/.agentix/credentials << 'EOF'
The shell example creates a hidden home directory and persists self-hosted connection settings outside the workspace.
Medium
Hidden file access
If credentials are already loaded from `~/.agentix/credentials`, skip to [Playbook](#playbook).
The instruction depends on loading values from the hidden home credentials file, confirming persistent filesystem access.
Medium
Hidden file access
Save the returned `apiKey` and `customerId` to `~/.agentix/credentials` immediately. Do not display
The skill directs the agent to write a newly issued API key and customer identifier into the hidden home credentials file.
Medium
Hidden file access
Reuse the same team across sessions. Do not create a new team each time. Save the returned `teamId`
The skill directs the agent to persist the returned team identifier in the hidden home credentials file for reuse.
Low
Hardcoded URL
2. If not set, default to `https://agentix.cloud`.
The skill sets agentix.cloud as the default API destination, so later operations intentionally communicate with an external service.
Low
Hardcoded URL
export AGENTIX_API_URL=https://agentix.cloud
This example configures agentix.cloud as the API endpoint used by the skill. The network destination is intentional and externally hosted.
Low
Hardcoded URL
export AGENTIX_API_URL=https://your-agentix-instance.example.com
The placeholder documents requests to a user-configured self-hosted endpoint. This is legitimate but confirms that the skill can contact non-marketplace services.
Low
Hardcoded URL
- **SaaS** (`$AGENTIX_API` is `https://agentix.cloud` or unset): Run the registration flow (Steps 1–
The SaaS path explicitly selects agentix.cloud and directs the agent into its remote registration flow.
Low
Hardcoded URL
AGENTIX_API_URL=http://localhost:3456
The localhost URL configures a self-hosted network service used by the skill. It confirms network capability even though the example remains on the host.
Low
Hardcoded URL
- **SaaS (default):** `https://agentix.cloud` — multi-tenant, requires registration and API key. Fol
The line identifies agentix.cloud as the default multi-tenant service and requires remote registration and API authentication.
Low
Hardcoded URL
- **Self-hosted:** Single team, no auth required. Set `AGENTIX_API_URL` to your instance URL (e.g.,
The line directs the skill to a user-selected self-hosted API. This is legitimate but confirms network access to a configurable service.
Low
Hardcoded URL
These steps apply only to `https://agentix.cloud`. Self-hosted users skip this section.
The line scopes the following workflow to agentix.cloud, confirming intended use of that external service.
Low
Hardcoded URL
POST https://agentix.cloud/register
The instruction sends a registration POST containing the user's name and email to agentix.cloud.
Low
Hardcoded URL
GET https://agentix.cloud/register/<token>
The instruction polls agentix.cloud with a registration token to retrieve account credentials.
Low
Hardcoded URL
POST https://agentix.cloud/teams
The instruction creates team data through an external agentix.cloud API request.
Low
Hardcoded URL
PATCH https://agentix.cloud/teams/$TEAM_ID
The instruction modifies a team through agentix.cloud while using an authorization credential.
Low
Hardcoded URL
{ "config": { "gitRepoUrl": "https://github.com/org/repo", "githubToken": "$GITHUB_TOKEN" } }
The configuration includes a GitHub repository URL, confirming integration with an external platform. Token exposure is covered by separate findings.
Low
Hardcoded URL
GET https://agentix.cloud/docs/getting-started # human getting started guide
The skill directs a GET request to the public agentix.cloud getting-started documentation endpoint.
Low
Hardcoded URL
GET https://agentix.cloud/docs/api-reference # full API reference
The skill directs a GET request to the public agentix.cloud API reference endpoint.
Low
Hardcoded URL
GET https://agentix.cloud/docs # interactive API explorer (Swagger)
The skill directs a GET request to the public agentix.cloud interactive documentation endpoint.
Low
Hardcoded URL
GET https://agentix.cloud/openapi.json # OpenAPI spec
The skill directs a GET request to the public agentix.cloud OpenAPI endpoint.
Risk Factors
⚙️ External commands (50)
SKILL.md:14 SKILL.md:16 SKILL.md:17 SKILL.md:19-25 SKILL.md:25-27 SKILL.md:27-31 SKILL.md:31-37 SKILL.md:37 SKILL.md:38-40 SKILL.md:40-53 SKILL.md:53-62 SKILL.md:62-69 SKILL.md:69-73 SKILL.md:73-74 SKILL.md:74 SKILL.md:80-86 SKILL.md:86-91 SKILL.md:91-93 SKILL.md:93-95 SKILL.md:95-99 SKILL.md:99-101 SKILL.md:101-103 SKILL.md:103 SKILL.md:105 SKILL.md:109-114 SKILL.md:114-116 SKILL.md:116 SKILL.md:122-127 SKILL.md:127-139 SKILL.md:139-141 SKILL.md:141-143 SKILL.md:143 SKILL.md:150-159 SKILL.md:159-163 SKILL.md:163-167 SKILL.md:167-171 SKILL.md:171-176 SKILL.md:176-178 SKILL.md:178-186 SKILL.md:186-189 SKILL.md:189-192 SKILL.md:192-194 SKILL.md:194-197 SKILL.md:197-199 SKILL.md:199-203 SKILL.md:203-208 SKILL.md:208-210 SKILL.md:210-212 SKILL.md:212 SKILL.md:218
🌐 Network access (17)
📁 Filesystem access (12)
🔑 Env variables (7)
Audited by: codex View Audit History →
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/agentix-cloud-agentix-ceo/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/agentix-cloud-agentix-ceo?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/agentix-cloud-agentix-ceo?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentix-cloud-agentix-ceo/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/agentix-cloud-agentix-ceo.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
agentix-cloud. (2026). agentix-ceo security audit report (audit version 5) [Author version 1.2.0]. Skillstore. https://skillstore.io/skills/agentix-cloud-agentix-ceo/audits/5BibTeX citation
@techreport{agentix-cloud-agentix-cloud-agentix-ceo-2026,
author = {agentix-cloud},
title = {agentix-ceo security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/agentix-cloud-agentix-ceo/audits/5},
note = {Author version 1.2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "agentix-ceo security audit report (audit version 5)"
version: "1.2.0"
type: report
authors:
- name: "agentix-cloud"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/agentix-cloud-agentix-ceo/audits/5"
identifiers:
- type: other
value: "skillstore:agentix-cloud-agentix-ceo:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: Medium 55
Architecture
100
Maintainability
87
Content
67
Community
91
Spec Compliance
What You Can Build
Coordinate Engineering Work
Create specialist roles, assign approved tasks, launch workers, and monitor delivery from one team view.
Run a Solo Project Team
Delegate implementation and review tasks to temporary workers while keeping project progress visible.
Operate a Self-Hosted Team
Connect to an internal Agentix instance, configure a stable team, and monitor worker activity.
Try These Prompts
Review Team Status
Show the Agentix team summary, active workers, and recent events. Do not create or update anything.
Plan Roles and Assignments
Review the current roles and ready tasks. Recommend missing roles and task assignments. Ask for approval before making changes.
Launch Approved Workers
In supervised mode, launch workers for the approved ready tasks. Report each worker identifier, assigned role, and task status.
Run a Guarded Backlog
Run the approved backlog with at most three concurrent workers. Stop before merges or credential changes and request approval.
Best Practices
- Use supervised mode until roles, permissions, budgets, and approval gates are verified.
- Provide scoped, short-lived credentials and confirm the destination before any secret transfer.
- Set explicit worker, cost, and time limits before launching multiple tasks.
Avoid
- Do not enable autopilot without concurrency, spending, and merge controls.
- Do not expose an unauthenticated self-hosted API beyond a trusted local interface.
- Do not place broad GitHub or Anthropic credentials in team configuration.
Frequently Asked Questions
Does this skill require Agentix SaaS?
No. It supports a self-hosted endpoint, but the documented self-hosted path lacks authentication and requires network safeguards.
Is an Anthropic API key required?
Yes, worker execution requires an Anthropic API key. Team inspection and configuration may work before workers are launched.
Where are Agentix credentials stored?
The skill documents a hidden plaintext file in the user home directory. Protect it with strict permissions or use a credential store.
Can the skill create roles and tasks?
Yes. It can list, create, update, and delete roles or tasks through the Agentix API.
What is the difference between supervised and autopilot modes?
Supervised mode requires approval for new work. Autopilot permits continuous planning, worker launches, reviews, and merges.
How can I keep control of repository changes?
Use supervised mode, restrict token permissions, and require approval before merges, role deletion, or credential updates.
Developer Details
Author
agentix-cloudLicense
MIT
Author version
v1.2.0
Skillstore revision
r2
Ref
9e952417e76879bc9d853e1b8b2cd6d6d8d4a1c2
Maintenance freshness
7/24/2026
Usage
11 downloads · 0 views
File structure
📄 SKILL.md