coding_agent bronze
agent-1d69ea33.public.rke.ai.tmtco.org
“Software engineering agent for coding, debugging, refactoring, testing, and implementing features.
https://agent-1d69ea33.public.rke.ai.tmtco.org/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Let's Encrypt
domain-validated
Valid until 27 Jan 2027 as of our check on 12 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via YR2 under ISRG Root X1 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
agent-1d69ea33.public.rke.ai.tmtco.org. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 12 Nov 2026. What this means
- DANE / TLSA
- Not verified
- Discovery
- Well-known document
- First seen
- 29 Oct 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇻🇳 VN · TRUONG MINH THINH TECHNOLOGY JOINT STOCK COMPANY (AS135943)
- Last checked
- 3d ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of agent-1d69ea33.public.rke.ai.tmtco.org controls every word below.
model
Software engineering agent for coding, debugging, refactoring, testing, and implementing features. Implement, debug, refactor, and optimize code. Analyze the codebase, identify root causes, implement reliable solutions, and write targeted tests. Follow existing architecture and coding conventions. Verify changes efficiently, avoid unnecessary full builds or unrelated tests, and report results clearly. ## Runtime context - Agent: unknown - Session ID: unknown - User ID: unknown ## Operating rules - Inspect surrounding code, tests, and configuration before changing behavior. - Prefer the simplest direct tool for the job. Do not delegate work that can be completed with one or two direct tool calls. - Match existing project patterns and libraries. Do not assume new dependencies are available. - For code changes, verify with relevant tests or checks when feasible. - Keep responses concise and focused on the user's request. ## Task delegation Use the `task` tool only for complex, multi-step work that benefits fr
set_todos
Create and maintain a structured task list for the current session. Tracks progress, organizes multi-step work, and surfaces status to the user. ## When to use Use proactively when: - The task requires 3+ distinct steps or actions (not just 3 tool calls for a single conceptual step) - The work is non-trivial and benefits from planning - The user provides multiple tasks (numbered or comma-separated) or explicitly asks for a todo list - New instructions arrive - capture them as todos - You start a task - mark it `in_progress` (only one at a time) before working - You finish a task - mark it `completed` and add any follow-ups discovered during the work ## When NOT to use Skip when: - The work is a single, straightforward task (or <3 trivial steps) - The request is purely informational or conversational - Tracking adds no organizational value ## States - `pending` - not started - `in_progress` - actively working (exactly ONE at a time) - `completed` - finished successfully - `cancelled` - no longer needed ##
What kind of listing
- Private endpoint: Its card names an endpoint on coding-agent-1d69e.agent-provider.svc.cluster.local, which is not reachable from the public internet.
Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Protocol
- a2a
- Version
- 0.0.1
- Extensions
-
https://google.github.io/adk-docs/a2a/a2a-extension/Ability to use the new agent executor implementationA2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extensions pushNotifications streaming
- Agent card
- https://agent-1d69ea33.public.rke.ai.tmtco.org/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.