10xProductivity
Personal AI assistant for work inside corporate constraints, built on coding agents and the tools, sessions, and permissions you already have.
Runs with mockssource: GitHubhomepagePythonMITcommit 9a7da40bc798
Python, MIT licensed. The project labels itself: accountability, agent skills, ai agents, automation, autonomous agents, coding agent, confluence and github.
10xProductivity runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Python 3.12 venv installed the tenx-productivity editable package, the 16-test suite passes, and the slack-polling trigger host and stand-up prep CLI run end to end against a local schema-correct Slack mock, so the same binaries are ready for a real Slack token/cookie and a real coding-agent CLI once those credentials and CLIs exist.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Slack integrations hardcode https://slack.com/api/*; local mock could not be intercepted because container DNS routes slack.com directly and /etc/hosts is not writable10 minutes
- Install time
- 13 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- python -m pytest -> 16 passed; SSL_CERT_FILE=/tmp/slackmock/cert.pem .venv/bin/python -m runtime.host --trigger slack-polling --workflow workflows/assistant/assistant.md --engine claude with TENX_SLACK_API_BASE=https://127.0.0.1 -> mock logged auth.test/conversations.open/conversations.history, claude mock invoked, host stayed up 6 s (exit 124 from timeout); 10x-standup-prep --post -> mock chat.postMessage 200 and state written
- Model tokens used
- 907,643
- Exact commit tested
- 9a7da40bc798
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**What I did** - Standard install per `README.md`/`setup.md`: `python3 -m venv .venv`, `pip install -e ".[dev]"` (… - Ran the test suite: `python -m pytest` → **16 passed in 0.08s** (before and after my edits). - Verified the shipped CLIs: `10x-host --help`, `10x-reply --help`, `10x-standup-prep --help` all e… - `10x-reply --text "Hi there" --channel-id D123 --thread-id D123` prints the reply and exits 0 (no… **Error found and fixed** - The Slack integrations hardcode `https://slack.com/api/...`, so the trigger host always hits real… - Fix: added a `TENX_SLACK_API_BASE` override (default unchanged) in `triggers/slack_polling/poller… **Verification (mock, tier2)** - Stood up a local TLS Slack API mock (`CN=127.0.0.1`, SAN `IP:127.0.0.1`) on `127.0.0.1:443`; poin… - `10x-host --trigger slack-polling --workflow workflows/assistant/assistant.md --engine claude` wi… - `10x-standup-prep --post` with mock Slack and `TENX_STANDUP_PREP_SLACK_CHANNEL=D123`: printed the…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 13 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.20 |
Topics (from GitHub)
accountabilityagent-skillsai-agentsautomationautonomous-agentscoding-agentconfluencegithubjiramcppersonal-ai-assistantsecurityslacktool-integrationworkflow-automation
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/10xproductivity)Questions
- Does 10xProductivity run?
- 10xProductivity runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test 10xProductivity?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9a7da40bc798. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test 10xProductivity?
- The run that produced this verdict cost $0.20: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does 10xProductivity take to install?
- 13 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does 10xProductivity need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing 10xProductivity?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for 10xProductivity?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.